Last 20 commits touching this section.
631459: What's new discoverability + workload availability for Azure Local deployment types (#21776) (#4502) * Proposal: add What's new in Azure Local hub and align multi-rack what's new - Add whats-new-hub.md as a single What's new landing page linking to hyperconverged, multi-rack, VM migration, and disconnected operations release notes. - Wire TOC What's new node to the hub and nest the four what's-new pages. - Remove monikers from multi-rack what's new and restructure to date-based sections (Azure Migrate style). * Fix TOC: remove href from parent What's new node, add hub as leaf child * Optimize what's new titles, descriptions, and H1 for search and AI retrievability * Fix YAML: remove colon from description values in what's new frontmatter * Replace What's new hub with TOC listing; add What's new column to deployment type guide * Merge workload availability matrix (#21748) into what's new PR; apply Manika's review comments and add reusable note include * Simplify workload availability to a workload list per Manika's feedback; drop Yes/No matrix * Link first mention of disconnected operations to its overview * Link Connected/Disconnected options in Step 1; remove duplicate disconnected links * Reword workload availability paragraph * Reword Connected mode description in Step 1 * Restore Yes/No workload availability matrix Co-authored-by: Ronmia Bess <61058899+ronmiab@users.noreply.github.com>
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-stack-docs-pr (branch main) (#4468) * Document missing Network Fabric metrics Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7e7c3fb6-7427-430d-88f3-389113eba846 * Update howto-replace-network-devices.md * Apply suggestion from @learn-build-service-prod-04[bot] Co-authored-by: learn-build-service-prod-04[bot] <274428985+learn-build-service-prod-04[bot]@users.noreply.github.com> * updating VDDK verbage * updating vddk wording * Clarify switched storage network recommendation * Update supported Network ATC intent groupings * Update azure-local/plan/cloud-deployment-network-considerations.md Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> * Update * Update * Update azure-local/plan/cloud-deployment-network-considerations.md Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> --------- Co-authored-by: Bhumika Shah <278596968+MSbhumika-shah@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: learn-build-service-prod-04[bot] <274428985+learn-build-service-prod-04[bot]@users.noreply.github.com> Co-authored-by: trumanbrown-msft <trumanbrown@microsoft.com> Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com> Co-authored-by: CristianEdwards <cedward@microsoft.com> Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> Co-authored-by: learn-build-service-prod-09[bot] <274431102+learn-build-service-prod-09[bot]@users.noreply.github.com> Copilot-Session: 7e7c3fb6-7427-430d-88f3-389113eba846
Merge pull request #21692 from ronmiab/rb-iscsi-minor Minor iSCSI planning doc cleanup: formatting, note placement, and wording (601975)
Merge pull request #21690 from ronmiab/rb-iscsi-fixes Refresh iSCSI network planning guidance: fix backup-network wording and add cross-links (601975)
Fix iSCSI backup-network wording and add cross-links (601975) - Correct mislabeled backup-network column in the disaggregated patterns overview - Clarify the iSCSI 6-port pattern uses an optional in-guest backup vNIC added after deployment, not a dedicated backup network - Add plan/deploy/concepts cross-links for iSCSI external storage
Update azure-local/plan/single-server-ip-requirements.md Co-authored-by: learn-build-service-prod-04[bot] <274428985+learn-build-service-prod-04[bot]@users.noreply.github.com>
Update azure-local/plan/cloud-deployment-network-considerations.md Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com>
Update azure-local/plan/cloud-deployment-network-considerations.md Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com>
Update azure-local/plan/cloud-deployment-network-considerations.md Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com>
591320: Azure Local TOC modernization: scenario-first navigation (#21093) * Add Azure Local TOC modernization mockup for stakeholder review Side-by-side scenario-first TOC mockup (TOC.modernization-mockup.yml) that implements the structure proposed in the Azure Local TOC Modernization & Content Consolidation Plan: L1 Connected | Disconnected | Workloads | Operate Azure Local L2 Hyperconverged | Disaggregated | Multi-rack | Small form factor L3 Evaluate | Plan | Set up | Operate (deployment-specific) L4 Tasks / articles Shared operations (monitor, update, troubleshoot, backup, migrate) are consolidated under a single Operate Azure Local branch. Workloads (VM, AKS, SQL, AVD, AI) are lifted out of deployment branches. Real hrefs from the current TOC.yml are reused where they map cleanly; TODO comments mark nodes that need new or consolidated articles. The live TOC.yml is unchanged. This file is not wired into docfx.json. * Refactor TOC mockup to strict scenario > deployment-model > Set up | Operate * Populate strict-alignment TOC mockup with all existing articles * Add missing disconnected troubleshoot articles to mockup * Consolidate all multi-rack articles under Connected > Multi-rack Per stakeholder request, all multi-rack articles now live exclusively under Connected > Multi-rack: - Multi-rack VM articles moved from Workloads > Azure Local VMs back into Connected > Multi-rack > Set up (create) and Operate (manage). - Multi-rack-specific concepts (compute, network fabric, load balancer, NAT, VM mgmt overview, security) consolidated under Set up. - Multi-rack reference (Network Cloud REST API, Network Fabric CLI, stack-hci-vm CLI) moved from top-level Reference into Operate > Reference. - Workloads > Azure Local VMs and top-level Reference now carry NOTE comments pointing to the multi-rack space. * Hyperconverged: apply scenario-first L4 phase grouping Set up restructured into six explicit L4 phases for a readable scenario flow: About / Evaluate / Plan / Prepare / Deploy / Enable add-ons. Use this as the template for Disaggregated, Multi-rack, and Small form factor. Set up changes: - New About phase (deployment-model intro only). - Plan phase wraps requirements, network reference patterns, Arc gateway, private endpoints, network considerations, security, env readiness, AD settings (previously flat L4 siblings). - New Prepare phase: prerequisites, AD prep, software download. - Deploy phase: install/register/deploy steps + Key Vault alt deploy + Deploy rack aware cluster (moved from Operate, since it's an end-to-end deploy workflow, not a day-2 op). - New Enable add-ons phase: Enable SDN + Enable external storage. Operate changes: - Rack aware cluster removed (moved to Set up > Deploy). - Migrate now precedes Troubleshoot (lifecycle order). Cross-cutting items relocated out of Hyperconverged Set up: - Compare to Windows Server -> top-level Concepts. - Release information / Known issues / Security updates -> top-level Overview as 'Current release' subgroup. - OEM license information / OEM license FAQ -> top-level Resources as 'OEM licensing' subgroup. Coverage: 399 unique articles preserved. * Propagate scenario-first L4 phase template to all Connected deployment models Disaggregated: - Set up reshaped to About / Plan / Prepare / Deploy / Enable add-ons. - 6 cross-cutting product items (Compare, Release info, Known issues, Security updates, OEM x2) removed; they live under top-level Concepts / Overview / Resources only. - Operate: Migrate moved before Troubleshoot (lifecycle order). - No Evaluate phase (no virtual deploy / jumpstart article today). Multi-rack: - Set up reshaped to About / Plan / Prepare / Deploy. - Concept articles grouped under Plan; CLI ext + prereqs under Prepare; L3 isolation, networking prereqs, SDN infra, VM workloads under Deploy. - No Evaluate / Enable add-ons phases today. Small form factor: - Set up reshaped to About / Evaluate / Plan / Prepare / Deploy. - About holds model intro + SFF-specific lifecycle (Known issues, FAQ). - Plan holds concepts + security/firewall. - Evaluate keeps VM-install path; Prepare = subscription; Deploy keeps install/connect/run/deploy applications/GPU workloads. - No Enable add-ons phase today. Coverage: 399 unique articles preserved. * Disconnected > Hyperconverged: apply minimal L4 phase grouping Set up reshaped to About / Plan / Deploy (no Evaluate, Prepare, or Enable add-ons phases since disconnected has no articles for those). Operate uses L4 grouping only where it pays off: - Manage (group: CLI, PowerShell, Policy, Billing) - Update disconnected operations (single article, kept flat at L4) - Back up and restore (group: Back up, Restore) - Monitor (disconnected) (single article, kept flat at L4) - Troubleshoot (disconnected) (existing group) Single-article verbs stay as flat L4 siblings rather than wrapping them in items: lists just to look uniform. Disaggregated / Multi-rack / SFF disconnected placeholders left as TODO pending confirmation those combos ship. Coverage: 399 unique articles preserved. * Disconnected > Hyperconverged > Operate: rename 'Manage' to 'Manage with Azure tooling' The bare 'Manage' bucket sat next to specific verbs (Update, Back up and restore, Monitor, Troubleshoot) and read ambiguous. The renamed form makes the bucket's intent (CLI / PowerShell / Policy / Billing admin) explicit. * Update strict-mode rules header: six-phase Set up, fixed Operate order, SFF/multi-rack carve-out * Exclude TOC.modernization-mockup.yml from azure-local docfx build The mockup is a side-file for stakeholder review and isn't a real TOC. Excluding it from both content groups stops the OPS validator from flagging schema-not-found and the filename-rule warnings against it. * Fix mockup file validation: add schema directive and rename - Prepend '### YamlMime:TableOfContent' so the Learn validator recognizes the schema (fixes schema-not-found error). - Rename TOC.modernization-mockup.yml -> toc-modernization-mockup.yml (lowercase + hyphens only, no dot separator) fixes filename-invalid-character warning and filename-incomplete suggestion. - Update docfx.json exclude entries to match the new filename. * Updated existing TOC for mockup * Updated to remove unnecessary aarticle * Updated TOC - Hyperconverged - Evaluate * Updated TOC * Add topology-first TOC mockup as alternative for stakeholder review Side-by-side comparison candidate to the connectivity-first L2 in TOC.yml. Excluded from build via docfx.json. Same Set up/Operate templates, same Manage L5 areas - only the L2 axis differs (topology-first vs connectivity-first). * Fully populate topology-first TOC mockup (all 500 hrefs from TOC.yml) Generated programmatically via .build-topology-first.js so both models share identical article inventory. Verified: same 500 unique hrefs in both TOC.yml and the topology-first side-file. * TOC modernization: add Find your deployment type, flatten Set up, consolidate What's new/Release notes/Operations at connectivity level * Apply suggestions from code review Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> * Remove topology-first mockup artifacts (PR #21102 closed) Drops .build-topology-first.js and toc-modernization-topology-first.yml, and reverts azure-local/docfx.json exclusions for both stale mockup files. Connectivity-first remains the sole proposal in TOC.yml. * TOC: move Operations to last position, rename Enable add-ons to Enable, promote Network ATC - Connected environments: Operations moved from before Hyperconverged to after Small form factor (last L2). Same in Disconnected environments.\n- Renamed 'Enable add-ons' L3 node to 'Enable' under Hyperconverged and Disaggregated (plus matching comment markers).\n- Concepts: replaced 'Host networking' L2 wrapper with a direct 'Network ATC' L2 entry pointing to the same article. * find-your-deployment-type: rewrite arc summary in active voice, second person, present tense Replaces the 'six-phase template' list-style sentence with an active-voice sentence aligned to the actual TOC (no Evaluate in the universal arc; Enable instead of Enable add-ons). * TOC comments: clean up after Operations move and other recent edits - Header docblock: fix layout (Operations is last), drop stale 'Not wired up to docfx.json' status, scope the Disconnected reduced-set claim to Hyperconverged only.\n- Connected/Disconnected env intros: reword to reflect that Operations now sits at the end of each connectivity branch.\n- Hyperconverged SET UP comment: drop the 'Evaluate' phase that doesn't exist for HCI.\n- Remove stale 'OPERATE' separator comments between Connected deployment models (Operate is consolidated under shared Operations).\n- Move misplaced 'SCENARIO 2: Disconnected environments' and 'WORKLOADS' section banners to sit above their actual L1 nodes (they were stranded inside the previous parent after the Operations move).\n- Move the Disconnected Operations NOTE (L4 template explainer) so it attaches to the relocated Operations node. * TOC: apply reviewer feedback — merge HC+Disagg, split Workloads, consolidate Resources - Move Billing under Resources (from Hyperconverged>Manage and Disconnected>Manage) - Nest Reference and Related under Resources as L2 - Merge Hyperconverged + Disaggregated into a single L2 under Connected, with separate Set up (hyperconverged)/Set up (disaggregated) and a shared Operate (moves the former Connected>Operations L2 inside as Operate L3) - Move Azure Local observability and Network ATC from top-level Concepts into the merged L2 as a Concepts L3 - Split top-level Workloads L1 into two L2s: one under Connected environments (all workload categories minus 3 disconnected leaves) and one under Disconnected environments (Azure Local VMs, AKS, and ACR in disconnected) Addresses PR feedback items R1-#1, #3, #4, #5 and R2-#1, #3. * TOC: move Network ATC overview from Concepts to Operate>Manage>Networking Groups the overview with its two how-tos (Add NICs / Replace a failed NIC in a Network ATC intent). Concepts L3 wrapper now contains only Azure Local observability. * TOC: move Azure Local observability to top-level Concepts L1 Removes the now-empty Concepts L3 wrapper inside Hyperconverged and disaggregated. Top-level Concepts L1 now contains Compare to Windows Server and Azure Local observability. * TOC: prune Disaggregated/Multi-rack/SFF TODO stubs under Disconnected environments Removes the three L2 placeholders that had no supporting documentation: - Disaggregated - Multi-rack - Small form factor Disconnected environments now lists only the deployment models that have existing content today (Hyperconverged), plus Workloads and Operations. Addresses reviewer feedback R1-#2 (partial): don't surface deployment models without docs on the disconnected pillar. * TOC: refresh header and section intro comments to match current structure Updates the doc comments to reflect the recent restructuring so future readers of the mockup see an accurate map of the layout: - Header layout diagram now shows the six current L1s (Overview, Connected environments, Disconnected environments, Concepts, Resources) and drops the removed top-level Workloads branch. - Header rules note the merged 'Hyperconverged and disaggregated' L2 on the connected pillar (with Set up (hyperconverged) / Set up (disaggregated) / Operate L3s) and clarify the disconnected pillar only surfaces Hyperconverged today. - Header adds a Workloads-split-by-connectivity rule and a Resources consolidation rule (Billing / Reference / Related now grouped under Resources). - Connected shared intro comment reflects the merged L2 with an internal Operate L3 instead of a separate top-level Operations node. - Disconnected shared intro comment reflects the removal of the Disaggregated / Multi-rack / SFF stubs. No structural TOC changes. * TOC: rewrite legend to match how FROM/REUSE/TODO are actually used The prior legend implied # FROM would appear on individual articles, but in practice it's used on section-header comments to trace a grouped block back to its original TOC section (only 1 of ~10 uses is on an article line). Update the legend text so it matches actual practice and adds usage location hints for REUSE and TODO. * Refine TOC labels and restructure Monitor - Rename "Set up (hyperconverged/disaggregated)" to "Install and deploy (...)" - Rename "Operate" to "Configure and manage"; add scope suffix on the shared Hyperconverged+Disaggregated node only - Move "Azure Local observability" from top-level Concepts to Configure and manage > Monitor > About - Group Monitor into subsections: About, Insights, Metrics and alerts, Health Service, Drift detection - Sync all header comments to match new node names * docs: rework Disconnected environments around Control Plane, refine Multi-rack/SFF/Overview/Resources per PM feedback * Updated TOC * docs: add install/deploy callout to control plane hardware article * docs: duplicate deployment-model TOC nodes for disconnected env * docs: remove deployment-model callout from control plane appliance * docs: merge Connected Configure-and-manage into one shared node * docs: fix REUSE tag gap, trim wordy comments, fix spacing * docs: fix customer intent persona in find-your-deployment-type * docs: nest Disconnected Install-and-deploy/Configure-and-manage under a Hyperconverged and disaggregated node * docs: hoist Deployment overview above Prepare in all four Install and deploy sections * docs: apply PM feedback -- suite grouping in Workloads, Partner Ecosystem + Odin under Resources, mirrored Overview headers - Connected > Workloads: grouped into AI suite / Data suite / Productivity suite / Bring your own apps / Other. Added Microsoft 365 Local, GitHub Enterprise Local, Azure IoT Operations. AKS nested under Bring your own apps (with note about planned move to AKS docs). - Disconnected > Workloads: grouped into AI suite / Productivity suite / Bring your own apps. Added AI workloads overview and Microsoft 365 Local. - Resources: removed 'Renaming to Azure Local'; added Odin for Azure Local link; added Partner Ecosystem section (solutions catalog, WAF); updated Pricing URL to azure.microsoft.com/pricing/details/azure-local/. - Mirrored Connected and Disconnected openers: wrapped What's new and Release notes under an Overview header in both sections. * docs: restructure Disconnected > Operate the Control Plane per PM feedback - Drop the 'Services' wrapper so Operate the Control Plane's children sit one level up. - Split the old 'Manage' node into siblings: Azure CLI, Azure PowerShell, and Backup and restore (nesting the back up and restore articles). - Add TODO stubs for Certificate rotation and Platform expansions. - Simplify labels (drop '(disconnected)' and 'disconnected operations' suffixes) to match the PM's list. - Reorder to PM's sequence: Update / Backup and restore / Certificate rotation / Monitor / Azure CLI / Azure PowerShell / Platform expansions / Troubleshoot / Azure Policy (kept and flagged -- PM's list didn't mention it). * docs: link Certificate rotation to disconnected-operations-cert-rotation.md (PR #21434) * docs: sync stale hrefs with upstream/main renames (cert rotation + SFF prepare-to-deploy) - disconnected-operations-cert-rotation.md -> disconnected-operations-certificate-rotation.md (renamed during PR #21504 merge). - small-form-factor-subscription-setup.md -> small-form-factor-prepare-to-deploy.md (renamed upstream); relabeled 'Set up subscription' -> 'Prepare to deploy' to match the article's broader scope. * docs: wire 17 new upstream articles into modernized TOC + relabel Key Vault node New article placements: - Deploy > 'Deploy using local identity with Azure Key Vault': add 'Overview' (deployment-local-identity-with-key-vault-overview.md) in all four blocks (Connected/Disconnected x Hyperconverged/Disaggregated). Also relabel the parent from 'Key Vault' to 'Azure Key Vault' to match the full product name and article titles. - Install and deploy (disaggregated) > Plan > Review disaggregated network reference patterns: add 'iSCSI 6-NIC disaggregated pattern' (Connected + Disconnected). - Configure and manage > Manage > SDN: add 'Optimize SDN availability and performance' (Connected + Disconnected). - Configure and manage > Manage > Systems: add 'Configure local availability zones' (Connected + Disconnected). - Configure and manage > Manage > GPUs: add 'REST APIs for GPU management' (Connected + Disconnected). - Disconnected > Operate the Control Plane > Backup and restore: add 5 post-restore recovery articles. - Connected > Workloads > Bring your own apps > Azure Local VMs: add new 'Confidential VMs' subsection (6 CVM articles, AB#600938). Verified: 897 TOC nodes, 0 broken relative hrefs against upstream/main + local file tree. * docs: rename Key Vault 'Overview' node to 'About local identity with Azure Key Vault' (4 places) * docs(find-your-deployment-type): align intro wording with style guide * docs(toc): trim comment noise for publication review Remove placeholder TOC nodes that were waiting on articles that don't exist yet (About workloads on Azure Local, Platform expansions), drop recurring # NOTE rationale blocks that duplicated content already documented in the PR description, and trim the mockup-specific header comment. Section markers, banner blocks, and inline # REUSE / # FROM / # TODO tags are preserved. * Update documentation via Quick Workspace * Update documentation via Quick Workspace * Update documentation via Quick Workspace * Update documentation via Quick Workspace * Update documentation via Quick Workspace * Update documentation via Quick Workspace * Update documentation via Quick Workspace --------- Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com> Co-authored-by: Ronmia Bess <content-mentor@example.com>
NetworkConsiderations2607Revamp (#21340) * NetworkConsiderations2607Revamp * PaulFeedbackfixes * LatestFixes * VarunFeedbackFixes * Apply suggestions for blocking issues from PR review Co-authored-by: Courtney Wales <62625502+Court72@users.noreply.github.com> --------- Co-authored-by: Courtney Wales <62625502+Court72@users.noreply.github.com>
Merge pull request #21357 from trumanbrown-msft/migrate-doc-update updating rest of doc guidance on DNS servers after 2607 announcement
Apply suggestions from code review Co-authored-by: learn-build-service-prod-03[bot] <274428581+learn-build-service-prod-03[bot]@users.noreply.github.com>
Update DNS server requirements for Azure Local Removed the section around workload LNETs allowing DNS to be hosted as VMs from the cloud deployment docs to avoid confusion to users.