Last 20 commits touching this section.
Reassign articles after org changes (#16843) * switch to clayton * Switch priyanka
PNP Edit: [AAC] Maintenance - Hybrid-ARB | Update Azure Hybrid Options + Getting Started articles (#16585) * Azure hybrid options - Complete article rewrite * Address hybrid options review feedback * Address hybrid architecture review comments * add spacing for clarity when reading * Reduce bullet spacing * updated spacing * Clarify disconnected operations eligibility * Refresh hybrid getting started guide Convert the hybrid Getting Started article to the YAML-plus-content pattern, move conceptual guidance and its diagram from Azure hybrid options, add browse metadata and a thumbnail, update navigation and inbound references, and keep detailed selection criteria in the options article. * Improve hybrid options workload flow Frame specialized service evaluation as the next step after selecting workload placement, infrastructure, and connectivity, and broaden the heading to reflect the services covered. * Fix hybrid getting started title Use singular architecture consistently in the YAML metadata and remove the duplicate H1 from the included Markdown body. * Address hybrid options review comments Add Azure Local operating limits and preview status, include Azure Arc-enabled Kubernetes in the decision-tree description, and preserve the intentional contributor attribution. * Update hybrid technology choices overview * Update technology choices review date * Clarify hybrid control plane options * Restore technology choices review date * Restore hybrid guide Markdown format Keep the Getting Started Architecture Guide as a standalone Markdown article, remove the YAML wrapper and its browse thumbnail, and update inbound links. * Clarify Azure IoT Operations offline limit Update the hybrid services diagram and accessible description to distinguish Azure Local disconnected operations from Azure IoT Operations' 72-hour offline window. Remove the redundant diagram footer. * Refine hybrid services diagram Replace the hybrid services diagram to keep Azure IoT Operations in the Edge and IoT category, clarify the Azure Local service list, and synchronize the accessible description. * Correct hybrid decision tree label Change the connected Azure Local path from "control plan" to "control plane" in the SVG and matching browse thumbnail. * Clarify Azure Local outage impact Document immediate cloud-dependent feature limitations, the 30-day reduced-functionality threshold, and AKS certificate-expiration risk during Azure connectivity loss. * Scope Azure Local sync guidance Qualify the documented 30-day synchronization and reduced-functionality behavior as applying to hyperconverged Azure Local deployments. * Apply suggestions from code review Co-authored-by: Chad Kittel <chad.kittel@gmail.com> * Update images * Address hybrid architecture review feedback Incorporate reviewer guidance on portability, edge AI, workload placement, recovery objectives, service wording, preview usage, and contributors. * Refine Azure Local reliability link text * Update hybrid options article date * improvements for Resiliency and recovery * Clarify hybrid deployment and connectivity guidance Correct Azure Local deployment taxonomy, distinguish ExpressRoute from VPN Gateway connectivity, and restore the overview article freshness date. * Update hybrid connectivity diagram label Rename the decision-tree branch to “Connectivity to Azure services” and refresh the matching browse thumbnail. * Clarify failover testing cadence Base Azure Local test-failover frequency on workload criticality, recovery objectives, business and compliance requirements, and material changes instead of a universal monthly interval. * Apply suggestion from @ckittel * Reference Sovereign Private Cloud in hybrid guidance * update ms.date * Reorder hybrid candidate approaches * Restore technology choices review date * Add private access selection guidance * Clarify Azure Arc machine support * Clarify VPN wording from review 5083098602 Addresses feedback from https://github.com/MicrosoftDocs/architecture-center-pr/pull/16383#pullrequestreview-5083098602 by distinguishing ExpressRoute from an encrypted site-to-site VPN in the article diagram and synchronized browse thumbnail. * get started article * options * edits * edits * edits * copilot * edits * not a tree * rearrange to fit template * Revert last 2 commits * revert toc * peer review cx * make png 3-2 * Apply batched suggestions from code review Co-authored-by: Chad Kittel <chad.kittel@gmail.com> * Fix link Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * . * . * . * fix --------- Co-authored-by: Neil Bird <nebird@microsoft.com> Co-authored-by: Chad Kittel <chad.kittel@gmail.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Sync category get-started includes with TOC (#16484) * Sync category get-started includes with TOC subtrees Reconcile all 14 managed get-started include files under docs/includes/ so each mirrors the section structure, order, nesting, and link membership of its corresponding category subtree in docs/toc.yml, while preserving curated non-TOC content such as prose and links to product documentation. - AI + Machine Learning: reordered AI guides section so direct links precede subsections; corrected two link texts. - Analytics: reordered sections to match subtree (Select a service, Solution ideas, Architectures, Guides); fixed several link texts. - Compute: restructured into Select a service, Solution ideas, Architectures, Guides, and a new SAP section with its own subsections; fixed link texts. - Containers: fully restructured into Select a service, Container guides, Kubernetes-based hosting (with nested solution ideas/architectures/guides and day-2 operations guide), and PaaS container hosting; disambiguated duplicate Application/Infrastructure headings; corrected several link texts; updated an anchor reference in the parent article. - Databases: restructured into Select a service, Solution ideas, Architectures, and Guides sections matching the subtree. - DevOps: reordered to Solution ideas, Architectures, Guides. - Identity: reordered to Solution ideas, Architectures, Guides. - Integration: restructured into Select a service, Solution ideas, Architectures, Guides. - Management + Governance: reordered to Architectures, then Guides. - Networking: restructured into Select a service, Architectures (Network topology, Network security), and Guides subsections. - Storage: reordered to Select a service, Solution ideas, Architectures. - Virtual Desktop: reordered to Architectures, then Guides. - Web applications: reordered to Solution ideas, Architectures, Guides, Hosting WordPress on Azure. IoT include already matched its subtree and needed no changes. * Apply suggestions from code review Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: learn-build-service-prod-01[bot] <274427437+learn-build-service-prod-01[bot]@users.noreply.github.com> Co-authored-by: Chad Kittel <chad.kittel@gmail.com> * Update docs/includes/analytics-get-started-include.md Co-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[bot]@users.noreply.github.com> * Fix nesting order in compute and container get-started includes Co-authored-by: ckittel <671075+ckittel@users.noreply.github.com> --------- Co-authored-by: azure-patterns-practices-assistant[bot] <316226753+azure-patterns-practices-assistant[bot]@users.noreply.github.com> Co-authored-by: Chad Kittel <chad.kittel@gmail.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: learn-build-service-prod-01[bot] <274427437+learn-build-service-prod-01[bot]@users.noreply.github.com> Co-authored-by: learn-build-service-prod-10[bot] <274431553+learn-build-service-prod-10[bot]@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: ckittel <671075+ckittel@users.noreply.github.com>
Fix redirected links in 3 articles Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
PnP edit - Microservices CI/CD pipeline on Kubernetes with Azure DevOps and helm (#16233) * docs: update CI/CD Kubernetes article with modern best practices - Add authentication and authorization section (Workload ID, OIDC, ACR integration) - Add supply chain security section (image signing, SBOM, vulnerability scanning) - Update master -> main branch references throughout - Add isolation best practices (network policies, resource quotas, Entra ID RBAC) - Fix Helm v2 -> v3 syntax (release name positional arg, helm list output) - Update .NET Core 3.1 -> .NET 8 references and Dockerfile publish path - Add SAST step to CI pipeline - Update deployment.extensions -> deployment.apps (deprecated API) - Add GitOps context (Flux, Argo CD) to alternatives section - Fix all relative links to absolute /en-us/azure/... paths - Add GitHub Actions as a first-class alternative alongside Azure Pipelines - Replace deprecated Pod Security Policies with Pod Security Standards Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * freshness: update ms.date to 03/27/2026 for CI/CD Kubernetes article Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * freshness: update author, ms.author to raykao, ms.date to 03/27/2026 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * freshness: update author, ms.author to raykao, ms.date to 03/27/2026 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update links to remove 'en-us' from URLs * Fixing links * Apply suggestion from @ShannonLeavitt Co-authored-by: Shannon Leavitt <47186198+ShannonLeavitt@users.noreply.github.com> * Update image signing link for Azure Key Vault Use absolute path to URL instead of relative * Clean up initial blank lines in CI/CD documentation Removed unnecessary blank lines at the beginning of the document. * Add contributors section to CI/CD Kubernetes content Added contributors section with details about the principal author. * Apply suggestions from code review Co-authored-by: Chad Kittel <chad.kittel@gmail.com> * Use site-relative link for image signing tutorial Convert the Notation with Azure Key Vault link from an absolute learn.microsoft.com/en-us URL to the site-relative form per Microsoft Learn link conventions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * De-dup GitHub Actions alternative section Remove the OIDC authentication and starter workflows bullets, which restate guidance already covered in the Alternatives section and the Authentication and authorization section. Cross-reference that earlier content and keep only the GitHub-specific capabilities (environments and protection rules, marketplace scanning actions). Addresses review feedback from @ckittel. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Clarify single shared ACR assumption Clarify that all microservices share a single Azure Container Registry instance, with a separate repository per microservice. Addresses review feedback from @ckittel. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Run SAST earlier in the PR CI build Move static application security testing (SAST) to run right after unit tests, before building and scanning the container image. SAST analyzes source code and has no dependency on the image, so running it earlier follows shift-left security practices and gives faster feedback. Addresses review feedback from @ckittel. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix malformed Azure DevOps build pipeline task list Split two list items that were merged onto single lines so the build pipeline tasks render as a clean nine-step ordered list. SAST runs before the container image is built and scanned, consistent with the CI flow described earlier in the article. Addresses review feedback from @ckittel. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Link to namespace-level RBAC with Entra ID Replace the stale /azure/aks/managed-azure-ad link and split the bullet into authentication and authorization. Reference the current control plane authentication doc and the Kubernetes RBAC with Microsoft Entra ID tutorial, which covers namespace-scoped Roles and RoleBindings. Addresses review feedback from @ckittel. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update stale Azure DevOps Helm task link Replace the old /pipelines/tasks/deploy/helm-deploy link, which redirects, with the current HelmDeploy@1 task reference and matching anchor text. Addresses review feedback from @ckittel. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Restructure auth/secrets guidance and add github product - Add the github product to the .yml metadata so GitHub appears in the article's product categories (the manual product line was removed). - Lead pipeline authentication with Azure Pipelines, then GitHub Actions, to match the article's AzDO-first framing. - Reframe the Microsoft Entra Workload ID bullet to make its CI/CD connection explicit (workloads the pipeline deploys). - Move the AKS-to-ACR integration guidance to the release pipeline section, where image pull happens, instead of the auth section. - Fold the long-lived credentials note into the Secrets management section. Addresses review feedback from @ckittel and @ShannonLeavitt. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Integrate supply chain security into pipeline steps Dissolve the standalone Supply chain security section and distribute its guidance into the steps where each practice belongs: - SBOM generation at the runtime container build step. - Vulnerability scanning now notes it gates publishing (de-duplicates the former standalone bullet). - A new image signing step after the image is pushed to the registry. - Admission control (Azure Policy for AKS) at the production deploy step. Addresses review feedback from @ckittel. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update two stale redirecting doc links Final link-staleness audit found two links that 200 only via redirect to a renamed page. Point them at the current canonical URLs: - Prometheus metrics overview moved from /azure-monitor/essentials/ to /azure-monitor/metrics/. - The Azure Pipelines CI/CD baseline architecture moved to /azure/devops/pipelines/architectures/devops-pipelines-baseline-architecture. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> * convert to md only * links * edits * images * edits * edit * edit * edit * edit * feedback * Update docs/microservices/ci-cd-kubernetes.md * fixing list formatting --------- Co-authored-by: Ray Kao <raykao@github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Shannon Leavitt <47186198+ShannonLeavitt@users.noreply.github.com> Co-authored-by: Ray Kao <ray.kao@microsoft.com> Co-authored-by: Chad Kittel <chad.kittel@gmail.com> Co-authored-by: Ray Kao <raykao@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: learn-build-service-prod-02[bot] <274428175+learn-build-service-prod-02[bot]@users.noreply.github.com> Co-authored-by: Diana Richards <103777760+v-dirichards@users.noreply.github.com>
Pipeline: Category Get Started Update: Container (#15762) * edits * Update container-get-started.md * Update container-get-started.md * Apply suggestions from code review Co-authored-by: Stephanie Savell <101299710+v-stsavell@users.noreply.github.com> * Apply suggestion from @v-stsavell * Apply suggestion from @v-albemi Co-authored-by: Mick Alberts <v-albemi@microsoft.com> * Apply suggestions from code review Co-authored-by: Jodi Martis <v-jodimartis@microsoft.com> * Remove 'Other resources' section from container guide Removed the 'Other resources' section that provided information on hybrid and multicloud container solutions. * Apply suggestion from @v-stsavell * Apply suggestions from code review Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> Co-authored-by: Stephanie Savell <101299710+v-stsavell@users.noreply.github.com> * edits * Update container-get-started.md --------- Co-authored-by: Mick Alberts <v-albemi@microsoft.com> Co-authored-by: Jodi Martis <v-jodimartis@microsoft.com> Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com>
Pipeline: [MAINT] AGC successor of AGIC Update (#16015) * AGC successor of AGIC Update Updated all AGIC to AGC and update the diagram to reflect as well * Address Copilot review: fix INCLUDE syntax, AGC/AGIC consistency, deploy link, remove unused svg - aks-agic.yml: fix broken INCLUDE syntax (missing closing bracket) which caused link-out-of-scope warning - aks-agc-content.md: restore concrete GitHub repo link in 'Deploy this scenario' section - aks-firewall-content.md: clarify that AGC terminates TLS at the AGC frontend (not at an Application Gateway listener); keep AGIC mention for the listener-based pattern - blue-green-deployment-for-aks-content.md: align terminology - AGC is the Azure-managed L7 LB, ALB controller is the in-cluster controller; replace leftover 'we use AGIC' with AGC + ALB controller - Remove unused media/aks-agic-updated.svg (orphan file, triggered image-name-incomplete suggestion) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * aks-agic-updated.svg update this * Fix three broken Learn site links flagged by validation - aks-agc-content.md L113: '/for-containers/how-to-multiple-namespaces' (404) -> /for-containers/how-to-multiple-site-hosting-gateway-api - aks-agc-content.md L229: '/for-containers/how-to-configure-waf-policy-ingress-api' (404) -> /for-containers/web-application-firewall - blue-green-deployment-for-aks-content.md L330: '/for-containers/alb-controller' (404) -> /for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller All replacement URLs verified live (HTTP 200). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Address Jack's review feedback: clarify AGC vs AGIC, update terminology - Clarify AGC is its own service, not dependent on Application Gateway - Replace AGIC-era language (listeners, ARM-applied config, CRS) with AGC-correct terminology (Gateway API, DRS 2.1) - Spell out 'Application Gateway for Containers' per marketing guidance - Correct multi-namespace claims (supported out of box) - Remove legally-loaded SLA percentages, link to official SLA docs - Switch to add-on quickstart link Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Refine descriptions for Application Gateway options * Clarify ALB controller's namespace ingestion capability Removed redundant information about ALB controller's capability to ingest events from multiple Kubernetes namespaces. * Rename aks-agic-updated.svg to aks-agc-architecture.svg and add AGCAccessLogs query reference Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Replace App Gateway concepts with Gateway API resources in sample diagram Map AppGW concepts to Gateway API equivalents in aks-agc-sample.svg: - HTTP listener -> Gateway - Rule (Basic) -> HTTPRoute (Match) - Back-end pool -> Service Also rename file aks-agic-sample.svg -> aks-agc-sample.svg and update reference. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix Microsoft.ServiceNetworking RP text overflow and update Ingress to Gateway in sample diagram - Wrap 'Microsoft.ServiceNetworking/trafficControllers resource provider' across 4 lines so text fits inside the box - Grow the box height downward so it no longer overlaps the Azure Resource Manager header - Replace remaining in-cluster Ingress boxes with Gateway (Listeners/Hostname/TLS certificate/Rules) for Gateway API alignment Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update author and ms.author to Vyshnavi-MSFT/vnamani Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add Vyshnavi Namani as a principal author * Address feedback: clarify Azure Firewall + AGC topology constraints AGC is always public/internet-facing today, so placing Azure Firewall in front of AGC isn't feasible. Recommend AGC in front of AzFW with AzFW between AKS and AGC via route tables, and call out that this design requires Azure CNI (not CNI Overlay). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix link for Application Gateway diagnostics settings Updated the link for enabling diagnostic settings for Application Gateway for Containers to the correct documentation page. * added feedback on frontend ip * Address John Downs review (non-multitenancy items): jumpbox/Bastion, Key Vault NOTE, drop classic AppGW, NGINX -> Gateway API, tab-link cleanup, Bicep-first, restructure Alternatives, expand ALB acronym, uptime SLA link, soften Let's Encrypt, remove Deploy section; remove find-pod-icon.js Multitenancy considerations to follow in a separate commit. * Clarify Application Gateway for Containers multitenancy framing - Clarify in the overview that Application Gateway for Containers is a single-tenant Azure resource, with multitenancy living inside the AKS cluster (namespaces, HTTPRoutes, tenant workloads). - Reword the taints-and-tolerations Performance Efficiency bullet to describe scheduling intent (avoid CPU/memory contention on dedicated nodes) in clearer language. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Clarify multitenancy description in AKS documentation Corrected wording for clarity regarding multitenancy in Application Gateway for Containers architecture. * Address John Downs review feedback with CELA pass - Rewrite intro to lead with Application Gateway for Containers and multitenancy; keep WAF as supporting protection. State Application Gateway for Containers single-tenancy explicitly. - Tighten multitenancy framing paragraph: remove conversational asides, fold in the "single ALB controller / multiple namespaces" callout that was previously at the end of Alternatives. - Potential use cases: fix "tenant" -> "multitenant", reorder bullets so Namespace-scoped RBAC follows Per-tenant TLS, italicize security policy resource name, replace slash with "and". - Add Deploy this scenario section with the multitenant sample diagram (aks-agc-sample.svg). - Remove broken #multitenancy-considerations anchor reference. - CELA pass across the article: remove "guarantee", "enhanced", "in a more secure manner", "more safe / fast / reliable", and similar non-factual qualifiers. Replace "enhanced capabilities" with the specific capabilities (Gateway API support, Azure-managed data plane). - Fix author byline format and product name casing. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update sample diagram and apply CELA pass to multitenancy framing - Replace aks-agc-sample.svg with updated Visio export: Gateway, HTTPRoute, Service, and Secret are now inside the AKS cluster boundary (not inside AGC); fix "TLS certification" -> "TLS certificate" - Delete redundant aks-agic-multitenancy.svg - Tighten the multitenancy NOTE for customer-facing voice and concision - CELA pass: remove "guarantee perfectly secure" / "sufficient" from Kubernetes isolation paragraph - Replace "shared frontend" -> "shared ingress" in use case bullets to avoid confusion with Azure Front Door (the Application Gateway for Containers Frontend resource name is preserved in body text) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Link AGC WAF doc in Next steps Replace the Application Gateway v1/v2 WAF policy link with the Web Application Firewall on Application Gateway for Containers doc, since this article is Application Gateway for Containers-only. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Clarify BYO vs Kubernetes-managed: recommend BYO for shared multitenant ingress Reviewer feedback: the multitenant shared-ingress pattern in this article requires a single shared Application Gateway for Containers Azure resource. The Kubernetes-managed model provisions one AGC per ApplicationLoadBalancer custom resource, so it does not fit this scenario. Explicitly recommend BYO and explain why. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Reframe BYO vs ALB Controller guidance as IMPORTANT callout Clarify that the multitenant architecture shares a single Application Gateway for Containers Azure resource, and explain why the BYO management model is the right fit (vs. managed by ALB Controller, which would create one Azure resource per tenant). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Refine AGfC multitenant guidance and replace sample diagram - Unify terminology to "ALB Controller-managed" (en-dash) across BYO vs managed comparison and the IMPORTANT callout - Replace aks-agc-sample.svg with simplified per-tenant view that includes HTTPRoute boxes inside each tenant namespace - Quality fixes from CELA + docs review: - Sentence-case headings for WAF pillars - Soften absolute claim on container image sizing - Fix /Azure/aks URL casing - Make main architecture alt text descriptive - Correct HTTP 403 status name to "Forbidden" Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Apply Niall's review feedback: clarity and active-voice edits Co-authored-by: Niall Glynn <glynnniall@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * edits * edits * Apply suggestions from code review Co-authored-by: Mick Alberts <v-albemi@microsoft.com> Co-authored-by: Stephanie Savell <101299710+v-stsavell@users.noreply.github.com> * Apply suggestion from @v-stsavell * Apply suggestions from code review Co-authored-by: Mick Alberts <v-albemi@microsoft.com> * Apply suggestions from code review Co-authored-by: Jodi Martis <v-jodimartis@microsoft.com> * redirect * edits --------- Co-authored-by: Vyshnavi-MSFT <vnamani@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Jodi Martis <v-jodimartis@microsoft.com> Co-authored-by: Niall Glynn <glynnniall@users.noreply.github.com> Co-authored-by: Mick Alberts <v-albemi@microsoft.com>
Pipeline: Freshness Pass for Use Azure Firewall to help protect an AKS cluster Doc (#15982) * Update AKS Firewall documentation with correct author information and date * markdown changes before review * Enhance AKS Firewall documentation with egress configuration details and SNAT capacity planning * Apply suggestions from code review Co-authored-by: Chad Kittel <chad.kittel@gmail.com> * Remove redundant DNAT rule explanation for Azure Firewall in AKS documentation * Apply suggestions from code review Co-authored-by: Chad Kittel <chad.kittel@gmail.com> * Remove extranous links (again) * Clarify application reference in Azure Firewall ingress controller documentation * convert md+yml pair to md file * fix * edits * Apply suggestions from code review Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> * fix * Apply suggestions from code review Co-authored-by: Chad Kittel <chad.kittel@gmail.com> Co-authored-by: Stephanie Savell <101299710+v-stsavell@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Mick Alberts <v-albemi@microsoft.com> Co-authored-by: Stephanie Savell <101299710+v-stsavell@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: learn-build-service-prod-08[bot] <274430765+learn-build-service-prod-08[bot]@users.noreply.github.com> Co-authored-by: Stephanie Savell <101299710+v-stsavell@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Stephanie Savell <101299710+v-stsavell@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: learn-build-service-prod-08[bot] <274430765+learn-build-service-prod-08[bot]@users.noreply.github.com> Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> Co-authored-by: Stephanie Savell <101299710+v-stsavell@users.noreply.github.com> * Update aks-firewall.md * Apply suggestions from code review Co-authored-by: Jodi Martis <v-jodimartis@microsoft.com> * Apply suggestions from code review Co-authored-by: Chad Kittel <chad.kittel@gmail.com> * Update baseline-aks-content.md --------- Co-authored-by: Sam Cogan <mail@samcogan.com> Co-authored-by: Chad Kittel <chad.kittel@gmail.com> Co-authored-by: learn-build-service-prod-07[bot] <274430390+learn-build-service-prod-07[bot]@users.noreply.github.com> Co-authored-by: Mick Alberts <v-albemi@microsoft.com> Co-authored-by: learn-build-service-prod-08[bot] <274430765+learn-build-service-prod-08[bot]@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: Jodi Martis <v-jodimartis@microsoft.com>
Pipeline: [Update] High availability for multitier AKS applications (#15970) * edits * edits * edits * edit * edit * edit * links * metadata * change to md * links * edits * Apply suggestions from code review Co-authored-by: Jodi Martis <v-jodimartis@microsoft.com> * svg * Apply suggestions from code review Co-authored-by: Chad Kittel <chad.kittel@gmail.com> * Apply suggestion from @v-albemi --------- Co-authored-by: Jodi Martis <v-jodimartis@microsoft.com> Co-authored-by: Chad Kittel <chad.kittel@gmail.com>
Pipeline: [Overcast] - Caching Best Practices (#15930) * Convert yml to md * Edit yml link in TOC * Review article * Fix anchor * Edits from proofread * Apply suggestions from code review Co-authored-by: Jodi Martis <v-jodimartis@microsoft.com> * Edits from copilot * Apply suggestions from code review Co-authored-by: Chad Kittel <chad.kittel@gmail.com> --------- Co-authored-by: Jodi Martis <v-jodimartis@microsoft.com> Co-authored-by: Chad Kittel <chad.kittel@gmail.com>
Fix link for Azure Savings Plan for Compute Updated the link for Azure Savings Plan for Compute to the correct overview page.