Skip to content
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

MLZ does not deploy Defender to every Spoke (Identity and SharedServices get skipped) Line #954 #719

Closed
LManning-Dev opened this issue Jul 18, 2022 · 0 comments · Fixed by #721
Labels
bug Something isn't working

Comments

@LManning-Dev
Copy link
Contributor

Description

MLZ does not deploy Defender to every Spoke (Identity and SharedServices get skipped) Line #954

Steps to Reproduce

Deploy mlz.bicep using 4 Subscriptions.

Expected behavior

Defender is enabled for all 4 Subscriptions

Actual behavior

Defender is only enabled for the Hub and the Operations Subscriptions

Screenshots

Additional context

When the defender.bicep is called for all the spokes, the scope is hard coded to the operations subscription
scope: subscription(operationsSubscriptionId)

To fix, the scope should point to the spoke's subscription

scope: subscription(spoke.subscriptionId)

Cloud (public, Azure Government, etc.): Commercial and Azure Government

@LManning-Dev LManning-Dev added the bug Something isn't working label Jul 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant