Update SNAT options article and flowchart to reflect revised retireme…#622
Merged
Conversation
…nt spec (March 2026 API change)
PR Description
## Summary
Update `articles/network/snat-options-for-azure-vm.md` and the associated decision flowchart `snat-options-for-azure-vm/flowchart-to-determine-snat-scenario.png` to reflect the latest official specification of the Azure default outbound access retirement (Tracking ID: 3T84-PZZ).
This is a companion update to the previously merged PR for `default-outbound-access-for-vms-will-be-retired.md`. Since the original article and flowchart were published in 2023, both the effective date and the implementation mechanism of the retirement have changed. Original content is preserved with strikethrough so readers can see what was revised.
## Key changes
- **Effective date**: ~~October 1, 2025~~ → **API versions released after March 31, 2026**
- **Scope**: ~~Per new Azure VM~~ → **Per new Virtual Network (subnet `defaultOutboundAccess = false` by default)**
- The judgment flow for "default outbound access enabled" now includes a subnet-level check.
## File changes
### `articles/network/snat-options-for-azure-vm.md`
- Added `updated: 2026-05-22` to front matter
- Top NOTE block: original retirement description preserved with strikethrough; revised 5-point summary added (March 2026 API change, VNet-level scope, existing VNets unaffected, older API versions behavior, Azure portal default)
- "構成パターンの一覧" section: timestamp updated from "2023 年 9 月現在" to "2026 年 5 月時点"; the deprecation note next to "既定の送信アクセス" item updated to the new spec
- "既定の送信アクセスの条件を満たしている？" subsection: added **条件3** describing the new subnet-level requirement (`defaultOutboundAccess` not set to `false`)
- "Azure 既定の送信アクセス" section warning: original red-text warning preserved with strikethrough; revised warning added with the 2026 spec
### `snat-options-for-azure-vm/flowchart-to-determine-snat-scenario.png`
Regenerated to incorporate the subnet-level decision and to reflect the new footnote content.
- **New decision node** inserted between "自動アウトバウンド NAT が有効な負荷分散規則** を定義している？" and "既定の送信アクセスの条件*** を満たしている？":
- **「プライベート サブネットではない？****」** (`defaultOutboundAccess ≠ false`)
- "はい" → existing default-outbound condition check
- "いいえ" → 接続不可 (routed cleanly below the result row to avoid crossing other connectors)
- **Footnote \*\*\*\*** updated to the revised spec: explains private-subnet semantics and the March 2026 API change; the previous retirement warning (now obsolete in its original form) is folded into the same footnote
- Layout polish: increased internal padding so text no longer touches box borders; uniform horizontal step of 320 px ensures no result-box overlap; canvas resized to 2580 × 1460
## References
- [Default outbound access in Azure | Microsoft Learn](https://learn.microsoft.com/ja-jp/azure/virtual-network/ip-services/default-outbound-access)
- Companion PR: update of `default-outbound-access-for-vms-will-be-retired.md` (already merged)
- Original announcement (Tracking ID: 3T84-PZZ)
## Notes for reviewers
- All 既存 explanatory content (SNAT mechanism, configuration patterns, comparison table, per-configuration details, etc.) is preserved unchanged.
- Q1/Q2 cross-link targets (judgment flowchart and configuration comparison anchors) remain valid.
- The flowchart PNG was regenerated programmatically. The script is kept in the session workspace (outside the repo) for traceability and future re-edits.
|
🥳 Thanks for your contribution! DetailsHi reviewers, could you review this PR? To checkout this PR and run preview server locally,git fetch origin pull/622/head:pr-622
git checkout pr-622
git submodule update -i
docker-compose upUser with write access can comment to accept this PR for deploying preview site: |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…nt spec (March 2026 API change)
PR Description
Summary
Update
articles/network/snat-options-for-azure-vm.mdand the associated decision flowchartsnat-options-for-azure-vm/flowchart-to-determine-snat-scenario.pngto reflect the latest official specification of the Azure default outbound access retirement (Tracking ID: 3T84-PZZ).This is a companion update to the previously merged PR for
default-outbound-access-for-vms-will-be-retired.md. Since the original article and flowchart were published in 2023, both the effective date and the implementation mechanism of the retirement have changed. Original content is preserved with strikethrough so readers can see what was revised.Key changes
October 1, 2025→ API versions released after March 31, 2026Per new Azure VM→ Per new Virtual Network (subnetdefaultOutboundAccess = falseby default)File changes
articles/network/snat-options-for-azure-vm.mdupdated: 2026-05-22to front matterdefaultOutboundAccessnot set tofalse)snat-options-for-azure-vm/flowchart-to-determine-snat-scenario.pngRegenerated to incorporate the subnet-level decision and to reflect the new footnote content.
defaultOutboundAccess ≠ false)References
default-outbound-access-for-vms-will-be-retired.md(already merged)Notes for reviewers