azure: mention that we search azure config

[isidentical]

You may disregard these recommendations if you used the Edit on GitHub button from dvc.org to improve a doc in place.

❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.

🐛 Please make sure to mention Fix #issue (if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.

Please choose to allow us to edit your branch when creating the PR.

Thank you for the contribution - we'll try to review it as soon as possible. 🙏

See: #2485

[shcheklein]

Question: some options - what does it mean?

---

I think we should describe all possible source and their priorities at the very beginning of the section. No chances people will get to this last paragraph. And if I understand this correctly (this files serves the same role as AWS credentials), this seems to be an important information that we want and should mention from the very beginning.

Something like: there are a few ways to define config values, in the order of their priority:

1. config files
2. env
3. DVC config

etc

(This is just an example, I don't know the details here)

[isidentical]

Question: some options - what does it mean?

#2703 (comment)

[shcheklein]

Thanks! That comment if you put it somewhere at the top of the document would be better - it's explicit, it explains the order clearly.

[jorgeorpinel]

we should describe all possible source and their priorities at the very beginning

Agree. Done in 8b035c1. But this section has gotten really complicated. This needs it's own guide I think (great first candidate for #1859 which keeps coming up BTW, so hopefully we can prioritize it).