-
Notifications
You must be signed in to change notification settings - Fork 301
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
Error 400 - azuread_group - Request contains a property with duplicate values #567
Comments
@manicminer here is the full request and response I pulled out of the debug log:
|
@mlcooper Thanks that's super helpful. As far as I can tell, there's nothing wrong with the request there, so this would appear to be an API bug? I would suggest raising this in a support ticket, and I will also do what I can to let the service team know (though you likely won't get an individual response). |
Thank you for taking a look, @manicminer. I have opened a support ticket with Azure and I will let you know what they find. |
Thanks again for reporting this @mlcooper. For additional context this error has made an appearance in other issues such as #478. Since it seems that this is due to an API bug, I've reported this upstream at microsoftgraph/msgraph-metadata#92 and will be closing this issue for now. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Terraform (and AzureAD Provider) Version
Affected Resource(s)
azuread_group
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Previously this code worked, but when I downgrade my azuread provider, to something like 2.1.0, it is still broken, but with a different error.
If I login to the Azure Portal or use the Azure CLI, using the same credentials (
az login
) as I do with TF, I am able to create a group in Azure Active Directory and assign an owner and member(s).Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: