-
Notifications
You must be signed in to change notification settings - Fork 336
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
Support Microsoft Graph #575
Comments
@tman5 Can you refer to question #573? It will help to you! Thank you very much! |
@tman5 Can you set "auth_source: cli" in the playbook to retry? The current 'ad' related modules only support CLI Credentials (az login). Thank you very much! |
In similar vein, I received this email from Microsoft today:
|
So @Fred-sun we currently cannot use a service principal to authenticate with if we aren't using graph yet? |
@tman5 I am successfully using a service principal with AD modules but had to grant access to the legacy APIs. See #573 (comment). |
See also: #477. |
@tman5 Would you give a try? those dependence file has upgrade to new. Thank you very much! |
Any hints on when support for the Microsoft Graph API (and removing dependency on deprecated Windows Azure Active Directory) is to be expected? |
@d2a-pnagel Being upgraded! |
@tman5 Already support msgraph-sdk in version 2.1.0. Thank you very much! |
SUMMARY
The Azure AD Graph API is no longer being updated come June 30, 2020. End of life is June 2022. I have tried to use the newer Graph API permissions for a service principal in Azure and it does not work. The Ansible module returns an insufficient permissions error.
ISSUE TYPE
COMPONENT NAME
I have tested with
azure_rm_adgroup_info
to get group info with a service principal having Graph API permissions and it will fail with insufficient permissions even though the service principal account has the permissions. The only workaround is to apply the legacy Microsoft Graph API permissions and then it works successfully.ADDITIONAL INFORMATION
Here is the post from Microsoft about the issue.
https://techcommunity.microsoft.com/t5/azure-active-directory-identity/update-your-applications-to-use-microsoft-authentication-library/ba-p/1257363
The text was updated successfully, but these errors were encountered: