Skip to content

Commit 2f35e2b

Browse files
authored
Update learn-pr/advocates/intro-ai-landing-zones/includes/1-introduction-landing-zones.md
1 parent 19ce210 commit 2f35e2b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

learn-pr/advocates/intro-ai-landing-zones/includes/1-introduction-landing-zones.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ These Azure landing zone design areas are as follows:
2121
- **Governance.** This design area addresses ensuring that governance policies and auditing are enforced and automated. An example would be notifications and alerts being generated when an element of the deployment's configuration drifts out of compliance due to configuration changes.
2222
- **Platform automation and DevOps.** This design element ensures that your organization leverages the right alignment of tools and templates to deploy landing zones and supporting resources.
2323

24-
![Image showing the eight different Azure landing zone design areas.](../media/landing-zone-decision-areas.png)
24+
![Table showing the eight different Azure landing zone design areas.](../media/landing-zone-decision-areas.png)
2525

2626
As a general rule, be prepared to balance requirements and functionality. Your journey to the most effective architecture for your organization's AI workloads will evolve over time as requirements change and you learn from your implementation.
2727

0 commit comments

Comments
 (0)