Azure / Azure/Microsoft-Defender-for-Cloud
There are several GUI changes needed
- Dominant language
- PowerShell
- Stars
- 1.9k
- Forks
- 871
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 1
Description
This is for labs 3 and 4. Also, I have built slide decks to go along with the labs to provide understanding of the topics prior to doing the labs. I have documented issues with the GUI in almost all the labs. If you would like them all, please let me know.
Lab 3
Editing Parameters (1): In the lab for this section, you will be asked to click on the assignment and then Parameters the Initiative Assignment page. There is no Initiative Assignment page. Instead, click on the assignment and then “Open in Azure Policy.”
Deny Storage account (4): Search for Secure transfer, Select secure transfer to storage account. At the top, select deny and then select the subscription and then select Change to deny
4-6 Select All Recommendations, then search
4-8 on scope and parameters set subscription and resource group to asclab
4-9 On recommendation page, select All Recommendations, Search SQL and find “Auditing on SQL server…..” Select the finding with 1 of 1 unhealthy resource. Nex t page select the server and then “Fix”, select the workspace and then fix.
5-6 Use Managed identity should be enabled for Container Apps Instead of in function apps. The Subscription owner policy can be skipped and the last 2 are in the list and can be selected.
When adding the custom initiative, do not navigate to Defender for Cloud. Stay in Policy and select assignments from the left. Then select Assign Initiative at the top. In basics, find the definition you built at the bottom. Make sure your scope is the Subscription, and then click review + Create, then create.
Lab 4
2-3: Select security policy, then Under Industry and regulatory standards select “add more standards”
2-6: After clicking “environmental settings”, select the subscription, and then continuous export.
4-9 There is not option for a sub-group. No need to create a sub-group.
Contributor guide
Research direction
No repository files or tests are named. Start with the Lab 3 and Lab 4 materials referenced in the issue, compare each listed step with the current Azure portal UI, and update the affected instructions. Done means the navigation, policy, recommendation, and security-setting steps match the current interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100