Azure / Azure/Microsoft-Defender-for-Cloud
Module‑1 Lab outdated automation is complete garbage
- Dominant language
- PowerShell
- Stars
- 1.9k
- Forks
- 871
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 1
Description
**Describe the bug**
Module‑1 Lab code is incredibly outdated and is now complete garbage.
**To Reproduce**
Steps to reproduce the behavior:
1- attempt to deploy this https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAzure-Security-Center%2Fmaster%2FLabs%2FFiles%2Flabdeploy.json
**Expected behavior**
It deploys as per documentation
**Additional context**
How did this get so out of date?
Contributor guide
Research direction
Start by reviewing the Module-1 Lab deployment referenced in the Azure portal link and the linked labdeploy.json template. Reproduce the deployment and compare its behavior with the documentation. Done means the lab deploys successfully as documented, though the issue does not identify specific outdated steps or files beyond the template.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100