-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Specified ARM Template Fails for Subsequent Runs #111440
Comments
H @Jtango18 , Thanks for sharing this feedback. We will look into this and update as appropriate. |
Hi @nofield ,@GithubMirek, Could you please look into this request, thanks. |
Hi @Jtango18, thanks for sharing this issue with us. Would you mind also sharing your payloads or correlation request ids so we can take a look at the requests? If you'd like to do further troubleshooting privately from this thread you can send an email to SQLAADFeedback@microsoft.com. What you're experiencing is expected behavior if the aad_admin_name parameter is modified between runs. It's not explained in this doc because the focus is on only an initial deployment, but our API doesn't support updates to the Azure AD administrator property through the Servers API. This is due to a difference in RBAC permission requirements between create server and updating Azure AD properties. If the aad_admin_name parameter is unchanged, it should be a no-op and succeed. To update the administrator, you can use the Microsoft.Sql/servers/administrators ARM template, which is documented here: https://learn.microsoft.com/en-us/azure/templates/microsoft.sql/servers/administrators?pivots=deployment-language-arm-template. I've also taken it as an action item to clearly articulate that the administrator properties are only create/read on the Servers API (whether that's the issue here or not). |
Hi @Jtango18 , thanks for contacting Microsoft! Looks like we were able to address your question so I'll go ahead and close out this Git Issue but please feel free to comment should you need anything further. Thanks again for reaching out and I hope you have a wonderful rest of your day! |
The ARM template specified fails on subsequent deployments. Works correctly the first time, the fails with the error
Invalid value given for parameter ExternalAdministratorLoginName. Specify a valid parameter value.
on all subsequent runsDocument Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: