Merge pull request #2275 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-18 22:11 UTC

Author: learn-build-service-prod[bot]

articles/azure-arc/kubernetes/extensions-release.md

@@ -1,6 +1,6 @@
 ---
 title: "Available extensions for Azure Arc-enabled Kubernetes clusters"
-ms.date: 02/18/2026
+ms.date: 03/18/2026
 ms.topic: how-to
 description: "See a list of extensions that are currently available for Azure Arc-enabled Kubernetes clusters. View Flux extension release notes."
 ms.custom:
@@ -204,17 +204,17 @@ The most recent version of the Flux v2 extension and the two previous versions (
 
 ### Deprecation and removal notice: Upcoming changes to `microsoft.flux` extension
 
-Several upstream Flux APIs that have been retired by the Flux project will be removed in an upcoming release of the `microsoft.flux` extension. These changes align with the Flux community's efforts to streamline and modernize the API surface.
+Several upstream Flux APIs that have been retired by the Flux project will be removed in upcoming releases of the `microsoft.flux` extension. These changes align with the Flux community's efforts to streamline and modernize the API surface.
 
 The following Flux APIs are being deprecated and will be removed:
 
-- Deprecated APIs in group `source.toolkit.fluxcd.io/v1beta1`
-- Deprecated APIs in group `kustomize.toolkit.fluxcd.io/v1beta1`
-- Deprecated APIs in group `helm.toolkit.fluxcd.io/v2beta1`
+- Deprecated APIs in group `source.toolkit.fluxcd.io/v1beta1` and `source.toolkit.fluxcd.io/v1beta2`
+- Deprecated APIs in group `kustomize.toolkit.fluxcd.io/v1beta1` and `kustomize.toolkit.fluxcd.io/v1beta2`
+- Deprecated APIs in group `helm.toolkit.fluxcd.io/v2beta1` abd `helm.toolkit.fluxcd.io/v2beta2`
 - Deprecated APIs in group `notification.toolkit.fluxcd.io/v1beta1`
 - Deprecated APIs in group `image.toolkit.fluxcd.io/v1beta1`
 
-For a complete list of deprecated APIs and their replacements, see the PRs linked in <https://github.com/fluxcd/flux2/issues/5474>.
+For more information, see <https://github.com/fluxcd/flux2/issues/5572>.
 
 **Required action:** To ensure continued compatibility and avoid disruptions, update your sources to remove references to deprecated APIs. Use the supported API versions for all impacted resources. We strongly recommend completing these steps before January 2026 to avoid deployment failures or resource reconciliation issues.
 

articles/azure-arc/servers/prerequisites.md

@@ -52,9 +52,11 @@ x86-64 (64-bit) architecture is fully supported, while [only some features may b
 | Azure Local                         |             |        |       |                                                                                                  |
 | Debian                              | 11          | ✅    | ❌    | Expected [limited support](#limited-support-operating-systems) date: 07/03/2026                  |
 | Debian                              | 12          | ✅    | ✅    |                                                                                                  |
+| Debian                              | 13          | ✅    | ✅    |                                                                                                  |
 | Oracle Linux                        | 7           | ✅    | ❌    |                                                                                                  |
-| Oracle Linux                        | 8           | ✅    | ❌    |                                                                                                  |
+| Oracle Linux                        | 8           | ✅    | ✅    |                                                                                                  |
 | Oracle Linux                        | 9           | ✅    | ❌    |                                                                                                  |
+| Oracle Linux                        | 10          | ✅    | ❌    |                                                                                                  |
 | Red Hat Enterprise Linux (RHEL)     | 7           | ✅    | ❌    |                                                                                                  |
 | Red Hat Enterprise Linux (RHEL)     | 8           | ✅    | ❌    |                                                                                                  |
 | Red Hat Enterprise Linux (RHEL)     | 9           | ✅    | ❌    |                                                                                                  |

articles/container-registry/container-registry-tutorial-base-image-update.md

@@ -88,7 +88,7 @@ az acr task create \
     --name baseexample1 \
     --image helloworld:{{.Run.ID}} \
     --arg REGISTRY_NAME=$ACR_NAME.azurecr.io \
-    --context https://github.com/$GIT_USER/acr-build-helloworld-node.git#master \
+    --context https://github.com/$GIT_USER/acr-build-helloworld-node.git#main \
     --file Dockerfile-app \
     --git-access-token $GIT_PAT
 ```
@@ -233,8 +233,8 @@ Now, move on to the next tutorial to learn how to trigger tasks on a defined sch
 <!-- LINKS - External -->
 [base-node]: https://hub.docker.com/_/node/
 [code-sample]: https://github.com/Azure-Samples/acr-build-helloworld-node
-[dockerfile-app]: https://github.com/Azure-Samples/acr-build-helloworld-node/blob/master/Dockerfile-app
-[dockerfile-base]: https://github.com/Azure-Samples/acr-build-helloworld-node/blob/master/Dockerfile-base
+[dockerfile-app]: https://github.com/Azure-Samples/acr-build-helloworld-node/blob/main/Dockerfile-app
+[dockerfile-base]: https://github.com/Azure-Samples/acr-build-helloworld-node/blob/main/Dockerfile-base
 
 <!-- LINKS - Internal -->
 [az-acr-build]: /cli/azure/acr#az-acr-build

articles/container-registry/container-registry-tutorial-private-base-image-update.md

@@ -184,12 +184,8 @@ az acr task list-runs --registry $ACR_NAME --output table
 
 If you completed the previous tutorial (and didn't delete the registry), you should see output similar to the following. Take note of the number of task runs, and the latest RUN ID, so you can compare the output after you update the base image in the next section.
 
-```azurecli
-az acr task list-runs --registry $ACR_NAME --output table
-```
-
 ```output
-UN ID    TASK            PLATFORM    STATUS     TRIGGER       STARTED               DURATION
+RUN ID    TASK            PLATFORM    STATUS     TRIGGER       STARTED               DURATION
 --------  --------------  ----------  ---------  ------------  --------------------  ----------
 ca12      baseexample2    linux       Succeeded  Manual        2023-11-21T00:00:56Z  00:00:36
 ca11      baseexample1    linux       Succeeded  Image Update  2023-11-20T23:38:24Z  00:00:34
@@ -273,8 +269,8 @@ In this tutorial, you learned how to use a task to automatically trigger contain
 <!-- LINKS - External -->
 [base-node]: https://hub.docker.com/_/node/
 [code-sample]: https://github.com/Azure-Samples/acr-build-helloworld-node
-[dockerfile-app]: https://github.com/Azure-Samples/acr-build-helloworld-node/blob/master/Dockerfile-app
-[dockerfile-base]: https://github.com/Azure-Samples/acr-build-helloworld-node/blob/master/Dockerfile-base
+[dockerfile-app]: https://github.com/Azure-Samples/acr-build-helloworld-node/blob/main/Dockerfile-app
+[dockerfile-base]: https://github.com/Azure-Samples/acr-build-helloworld-node/blob/main/Dockerfile-base
 
 <!-- LINKS - Internal -->
 [az-acr-build]: /cli/azure/acr#az-acr-build

docfx.json

@@ -244,7 +244,8 @@
       "ms.subservice": {
         "articles/azure-arc/kubernetes/**/*.md": "azure-arc-kubernetes",
         "articles/azure-arc/servers/**/*.md": "azure-arc-servers",
-        "articles/azure-arc/container-storage/**/*.md": "azure-arc-container-storage"
+        "articles/azure-arc/container-storage/**/*.md": "azure-arc-container-storage",
+        "articles/azure-arc/workload-orchestration/**/*.md": "workload-orchestration"        
       },
       "searchScope": {
         "articles/azure-arc/**/*.md": [