Skip to content

docs: refresh standalone diagram from revised Visio export - #793

Merged
Paulo Lacerda (placerda) merged 1 commit into
mainfrom
release/4.3.0
Oct 15, 2026
Merged

Paulo Lacerda (placerda) merged 1 commit into
mainfrom
release/4.3.0

Conversation

@placerda

Copy link
Copy Markdown
Contributor

Summary

Documentation-only refresh of media/architecture_zero_trust.png from page 2 (Root / Standalone) of the revised Visio PDF export, preserving the existing Standalone image path. This targets main under the user's explicit documentation-image exception.

The existing release/4.3.0 branch is reused solely to satisfy the repository branch gate. This is not a new release: the version, manifest, and existing v4.3.0 tag remain unchanged. No runtime, policy, workflow, Azure, or release changes are included, and the source PDF is not uploaded.

Image evidence

  • Lossless RGB PNG, rendered at 300 DPI, 6077 x 4605 pixels.
  • Parent session checked PNG CRC integrity, DPI metadata, and the rendered image visually.
  • Revised PDF SHA-256: 52367ee8d0d6eb1998a8dadc69c72c0f73d7e06810f0c0e10ff79a9003af7931.
  • PNG SHA-256: 5c16b2e8fee39268645596b15883788b9b6fb149a11d0aabcde3de51d4f3852c.
  • Source HEAD: 8bdd6a20f3af71ef5c6119144505af8384abafc4; the only changed file against main is media/architecture_zero_trust.png.

Related documentation

The central-platform diagram (PDF page 1) and gateway diagram (PDF page 3) were published separately to Azure/AI-Landing-Zones main at 9671ae1ab9c81b5a70fdab1c34a4399a61cb05cd, with strict MkDocs validation passing. The conceptual overview was preserved.

Replace only the standalone PNG using the revised PDF at 300 DPI. No runtime, version or release changes.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@placerda
Paulo Lacerda (placerda) merged commit 574a3f7 into main Oct 15, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant