-
Notifications
You must be signed in to change notification settings - Fork 192
Connect using BYOT via a Managed Identity in Azure Functions #46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is a scenario that is definitely on our roadmap. |
This will also enable transparent auth in Cloud Shell |
This functionality is dependent on work we are doing in .Graph SDK .NET 2.0. |
Would be awesome if would could use the module in Azure Functions. |
Would love to see an accesstoken parameter. This would leave the option open to do cross-tenant/multi-tenant queries. |
This is for Connect-Graph having a -token option to allow bypassing the normal code. |
@colinrippeyfinarne we have added a new CmdLet |
Thanks for the details, but I hope that this is not the resolution to the request? I hope you are still looking to add a -Token parameter to the Connect commandlet as I want to use all the lovely wrapper commandlets after connecting via Connect. It will of course be useful to have the Invoke-GraphRequest commandlet, but surely one of the points of this library is to abstract away having to craft up raw urls and deal in a higher level scripting model? Thanks again though for the details, it will be very useful. |
@colinrippeyfinarne We have added |
Brilliant, thanks for the update. |
Uh oh!
There was an error while loading. Please reload this page.
I have tons of use cases for running Powershell scripts in Azure Functions. What I do at the moment is obtain my Managed Identity bearer token (which I have previously granted permissions to) and the use the Invoke-WebRequest commandlet against the raw Graph API.
It would be great if as part of the Connect commandlet I was able to either pass in my already obtained bearer token, or even maybe ask the Connect commandlet to go get it for me.
AB#5613
The text was updated successfully, but these errors were encountered: