log activities from subscriptions used in an MLZ deployment into the Operations log analytics workspace #412
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
glennmusa
suggested changes
Sep 14, 2021
Co-authored-by: Glenn Musa <[email protected]>
Co-authored-by: Glenn Musa <[email protected]>
Co-authored-by: Glenn Musa <[email protected]>
Co-authored-by: Glenn Musa <[email protected]>
glennmusa
reviewed
Sep 15, 2021
Co-authored-by: Glenn Musa <[email protected]>
operations module naming Co-authored-by: Glenn Musa <[email protected]>
module naming convention update Co-authored-by: Glenn Musa <[email protected]>
Co-authored-by: Glenn Musa <[email protected]>
Co-authored-by: Glenn Musa <[email protected]>
Co-authored-by: Glenn Musa <[email protected]>
glennmusa
changed the title
|
Awesome! This all deployed and seemed to be working in my manual deployment. I have a suggestion to merge into your work in #414 for naming things at the root module instead of in the component module. If you want to take a look, and if it's a good idea, merge it back into this branch? |
glennmusa
approved these changes
Sep 16, 2021
Breanna-Stryker
added a commit
that referenced
this pull request
Sep 17, 2021
* prefer local backends for terraform * add a Bicep Azure Sentinel module (#385) * Remove Client/Client Secret/Tenant Vars from Terraform Templates Co-authored-by: Bree Stryker <[email protected]> * add workflows to lint and build .bicep modules (#400) * disable verbose lint output (#402) * optionally deploy built-in Policy Initiatives for NIST 800-53, CMMC Level 3, or DOD IL5 (#397) * log activities from subscriptions used in a deployment into the Operations log analytics workspace (#412) * optionally deploy Azure Bastion Host from the base deployment (#406) Co-authored-by: Vidya Bala <[email protected]> Co-authored-by: Bree Stryker <[email protected]> Co-authored-by: Glenn Musa <[email protected]> Co-authored-by: Shawn Gibbs <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds a diagnostic setting that pushes logs from activity logging into the operations RG's log analytics workspace. This is a subscription level deployment so it hangs around after deleting RG's and will need to be deleted.
Issue reference
The issue this PR will close: #373
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:
shellcheck.vscode/extensions.json.)