There should be a secure way to pass secrets or keys when making an API call (e.g. web.contents) in Power Query M.
Suggestions:
A) Make it possible to enter and edit secrets in Power Quer...
The suggestions (A, B, C) don't need to be implemented together. They can be implemented separately.
If A) gets implemented, there will perhaps not be a need for B).
The main Idea is to make it possible to include secured and hidden secrets in cases where the regular Data Source Credentials don't apply, e.g. in the web.contents connector.
