-
Notifications
You must be signed in to change notification settings - Fork 517
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
💡 Feature Request - Change deployment scope for MG Diagnostics #338
Comments
Great ask @chrisking81 and thanks for raising this following our chat this afternoon. We will triage and prioritise this on our scrum call today. cc: @lachaves |
14 tasks
jtracey93
added a commit
that referenced
this issue
Nov 3, 2022
* Updated README to show new scope at mg level * Changes to mgDiagSettingsAll.bicep with new mg deployment scope * Added mgDiagSettingsAll as a new orchestration module to the list * Fixed a URL tfor step 4.1 to point to the corret module * Update infra-as-code/bicep/orchestration/mgDiagSettingsAll/mgDiagSettingsAll.bicep Co-authored-by: Jack Tracey <41163455+jtracey93@users.noreply.github.com> * Changed the test-pipelines to reflec the deployment at the mg level now Co-authored-by: Luis Chaves <luchaves@microsoft.com> Co-authored-by: Jack Tracey <41163455+jtracey93@users.noreply.github.com>
#372 merged so closing |
ghost
locked as resolved and limited conversation to collaborators
Dec 3, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thanks for the recently added modules to set the diagnostic settings on the MG hierarchy.
My customer would like to use these but is currently blocked, due to the fact that the orchestration module is a 'tenant' scoped deployment.
My customer has no permissions to \ or Tenant Root Group, due to segregation of duties.
Could we please investigate whether we can change the orchestration module to be a 'management group' scoped deployment?
The text was updated successfully, but these errors were encountered: