update the Bicep extensibility provider name to extension

Author: mumian

.openpublishing.redirection.azure-resource-manager.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path_from_root": "/articles/aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider.md",
+      "redirect_url": "/articles/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/app-service-web/app-service-move-resources.md",
       "redirect_url": "/azure/azure-resource-manager/management/move-limitations/app-service-move-limitations",
@@ -1155,6 +1160,11 @@
       "redirect_url": "/azure/azure-resource-manager/bicep/compare-template-syntax",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/azure-resource-manager/bicep/bicep-extensibility-kubernetes-provider.md",
+      "redirect_url": "/azure/azure-resource-manager/bicep/bicep-kubernetes-extensions",
+      "redirect_document_id": false
+    },    
     {
       "source_path_from_root": "/articles/azure-resource-manager/templates/complete-mode-deletion.md",
       "redirect_url": "/azure/azure-resource-manager/templates/deployment-complete-mode-deletion",

articles/aks/learn/media/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider/aks-store-application.png renamed to articles/aks/learn/media/quick-kubernetes-deploy-bicep-kubernetes-extension/aks-store-application.png

@@ -1,6 +1,6 @@
 ---
-title: Deploy an AKS cluster using the Bicep extensibility Kubernetes provider
-description: Learn how to quickly deploy a Kubernetes cluster using the Bicep extensibility Kubernetes provider and deploy an application in Azure Kubernetes Service (AKS). 
+title: Deploy an AKS cluster using the Bicep Kubernetes extension
+description: Learn how to quickly deploy a Kubernetes cluster using the Bicep Kubernetes extension and deploy an application in Azure Kubernetes Service (AKS). 
 author: tamram
 
 ms.topic: quickstart
@@ -11,15 +11,15 @@ ms.author: tamram
 #Customer intent: As a developer or cluster operator, I want to quickly deploy an AKS cluster and deploy an application so that I can see how to run applications using the managed Kubernetes service in Azure.
 ---
 
-# Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using the Bicep extensibility Kubernetes provider (preview)
+# Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using the Bicep Kubernetes extension (preview)
 
 Azure Kubernetes Service (AKS) is a managed Kubernetes service that lets you quickly deploy and manage clusters. In this quickstart, you:
 
-- Deploy an AKS cluster using the Bicep extensibility Kubernetes provider (preview).
+- Deploy an AKS cluster using the Bicep Kubernetes extension (preview).
 - Run a sample multi-container application with a group of microservices and web front ends simulating a retail scenario.
 
 > [!IMPORTANT]
-> The Bicep Kubernetes provider is currently in preview. You can enable the feature from the [Bicep configuration file](../../azure-resource-manager/bicep/bicep-config.md#enable-experimental-features) by adding:
+> The Bicep Kubernetes extension is currently in preview. You can enable the feature from the [Bicep configuration file](../../azure-resource-manager/bicep/bicep-config.md#enable-experimental-features) by adding:
 >
 > ```json
 > {
@@ -74,7 +74,7 @@ Save a copy of the file as `main.bicep` to your local computer.
 
 To deploy the application, you use a manifest file to create all the objects required to run the [AKS Store application](https://github.com/Azure-Samples/aks-store-demo). A [Kubernetes manifest file][kubernetes-deployment] defines a cluster's desired state, such as which container images to run. The manifest includes the following Kubernetes deployments and services:
 
-:::image type="content" source="media/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider/aks-store-architecture.png" alt-text="Screenshot of Azure Store sample architecture." lightbox="media/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider/aks-store-architecture.png":::
+:::image type="content" source="media/quick-kubernetes-deploy-bicep-kubernetes-extension/aks-store-architecture.png" alt-text="Screenshot of Azure Store sample architecture." lightbox="media/quick-kubernetes-deploy-bicep-kubernetes-extension/aks-store-architecture.png":::
 
 - **Store front**: Web application for customers to view products and place orders.
 - **Product service**: Shows product information.
@@ -323,7 +323,7 @@ To deploy the application, you use a manifest file to create all the objects req
 1. Press <kbd>Ctrl+Shift+P</kbd> to open **Command Palette**.
 1. Search for **bicep**, and then select **Bicep: Import Kubernetes Manifest**.
 
-    :::image type="content" source="./media/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider/bicep-extensibility-kubernetes-provider-import-kubernetes-manifest.png" alt-text="Screenshot of Visual Studio Code import Kubernetes Manifest." lightbox="./media/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider/bicep-extensibility-kubernetes-provider-import-kubernetes-manifest.png":::
+    :::image type="content" source="./media/quick-kubernetes-deploy-bicep-kubernetes-extension/bicep-kubernetes-extension-import-kubernetes-manifest.png" alt-text="Screenshot of Visual Studio Code import Kubernetes Manifest." lightbox="./media/quick-kubernetes-deploy-bicep-kubernetes-extension/bicep-kubernetes-extension-import-kubernetes-manifest.png":::
 
 1. Select `aks-store-quickstart.yaml` from the prompt. This process creates an `aks-store-quickstart.bicep` file in the same folder.
 1. Open `main.bicep` and add the following Bicep at the end of the file to reference the newly created `aks-store-quickstart.bicep` module:
@@ -388,7 +388,7 @@ It takes a few minutes to create the AKS cluster. Wait for the cluster successfu
 1. Find the **store-front** service and copy the value for **External IP**.
 1. Open a web browser to the external IP address of your service to see the Azure Store app in action.
 
-    :::image type="content" source="media/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider/aks-store-application.png" alt-text="Screenshot of AKS Store sample application." lightbox="media/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider/aks-store-application.png":::
+    :::image type="content" source="media/quick-kubernetes-deploy-bicep-kubernetes-extension/aks-store-application.png" alt-text="Screenshot of AKS Store sample application." lightbox="media/quick-kubernetes-deploy-bicep-kubernetes-extension/aks-store-application.png":::
 
 ## Delete the cluster
 

articles/aks/learn/media/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider/aks-store-architecture.png renamed to articles/aks/learn/media/quick-kubernetes-deploy-bicep-kubernetes-extension/aks-store-architecture.png

@@ -8,7 +8,7 @@ ms.date: 06/03/2024
 
 # Imports in Bicep
 
-This article describes the syntax you use to export and import shared functionality, as well as namespaces for Bicep extensibility providers.
+This article describes the syntax you use to export and import shared functionality, as well as namespaces for Bicep extensions.
 
 ## Exporting types, variables and functions
 
@@ -80,7 +80,7 @@ output greeting string = sayHello('Bicep user')
 output exampleObject myImports.myObjectType = exampleObject
 ```
 
-## Import namespaces and extensibility providers (Preview)
+## Import namespaces and extensions (Preview)
 
 > [!NOTE]
 > The experimental feature `extensibility` must be enabled from the [Bicep config file](./bicep-config.md#enable-experimental-features) to use this feature.
@@ -94,25 +94,25 @@ import '[email protected]'
 
 Both `az` and `sys` are Bicep built-in namespaces. They are imported by default. For more information about the data types and the functions defined in `az` and `sys`, see [Data types](./data-types.md) and  [Bicep functions](./bicep-functions.md).
 
-The syntax for importing Bicep extensibility providers is:
+The syntax for importing Bicep extensions is:
 
 ```bicep
-import '<provider-name>@<provider-version>'
+import '<extension-name>@<extension-version>'
 ```
 
-The syntax for importing Bicep extensibility providers which require configuration is:
+The syntax for importing Bicep extensions which require configuration is:
 
 ```bicep
-import '<provider-name>@<provider-version>' with {
-  <provider-properties>
+import '<extension-name>@<extension-version>' with {
+  <extension-properties>
 }
 ```
 
-For an example, see [Bicep extensibility Kubernetes provider](./bicep-extensibility-kubernetes-provider.md).
+For an example, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
 
 ## Next steps
 
 - To learn about the Bicep data types, see [Data types](./data-types.md).
 - To learn about the Bicep functions, see [Bicep functions](./bicep-functions.md).
-- To learn about how to use the Kubernetes provider, see [Bicep extensibility Kubernetes provider](./bicep-extensibility-kubernetes-provider.md).
-- To go through a Kubernetes provider tutorial, see [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes provider.](../../aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider.md).
+- To learn about how to use the Kubernetes extension, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
+- To go through a Kubernetes extension tutorial, see [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes extension.](../../aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension.md).

articles/aks/learn/media/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider/bicep-extensibility-kubernetes-provider-import-kubernetes-manifest.png renamed to articles/aks/learn/media/quick-kubernetes-deploy-bicep-kubernetes-extension/bicep-kubernetes-extension-import-kubernetes-manifest.png

@@ -1,17 +1,17 @@
 ---
-title: Bicep extensibility Kubernetes provider
-description: Learn how to Bicep Kubernetes provider  to deploy .NET applications to Azure Kubernetes Service clusters.
+title: Bicep Kubernetes extension
+description: Learn how to Bicep Kubernetes extension to deploy .NET applications to Azure Kubernetes Service clusters.
 ms.topic: conceptual
 ms.custom: devx-track-bicep, devx-track-dotnet
-ms.date: 03/20/2024
+ms.date: 06/27/2024
 ---
 
-# Bicep extensibility Kubernetes provider (Preview)
+# Bicep Kubernetes extension (Preview)
 
-The Kubernetes provider allows you to create Kubernetes resources directly with Bicep. Bicep can deploy anything that can be deployed with the [Kubernetes command-line client (kubectl)](https://kubernetes.io/docs/reference/kubectl/kubectl/) and a [Kubernetes manifest file](../../aks/concepts-clusters-workloads.md#deployments-and-yaml-manifests).
+The Kubernetes extension allows you to create Kubernetes resources directly with Bicep. Bicep can deploy anything that can be deployed with the [Kubernetes command-line client (kubectl)](https://kubernetes.io/docs/reference/kubectl/kubectl/) and a [Kubernetes manifest file](../../aks/concepts-clusters-workloads.md#deployments-and-yaml-manifests).
 
 > [!NOTE]
-> Kubernetes provider is not currently supported for private clusters:
+> Kubernetes extension is not currently supported for private clusters:
 > 
 > ```bicep
 > resource AKS 'Microsoft.ContainerService/managedClusters@2023-01-02-preview' = {
@@ -24,7 +24,6 @@ The Kubernetes provider allows you to create Kubernetes resources directly with
 > }
 > 
 > ```
-> 
 
 ## Enable the preview feature
 
@@ -38,12 +37,12 @@ This preview feature can be enabled by configuring the [bicepconfig.json](./bice
 }
 ```
 
-## Import Kubernetes provider
+## Import Kubernetes extension
 
 To safely pass secrets for the Kubernetes deployment, you must invoke the Kubernetes code with a Bicep module and pass the parameter as a secret.
-To import the Kubernetes provider, use the [import statement](./bicep-import-providers.md). After importing the provider, you can refactor the Bicep module file as usual, such as by using variables, parameters, and output. By contract, the Kubernetes manifest in YML doesn't include any programmability support.
+To import the Kubernetes extension, use the [import statement](./bicep-import.md). After importing the extension, you can refactor the Bicep module file as usual, such as by using variables, parameters, and output. By contract, the Kubernetes manifest in YML doesn't include any programmability support.
 
-The following sample imports the Kubernetes provider:
+The following sample imports the Kubernetes extension:
 
 ```bicep
 @secure()
@@ -55,7 +54,7 @@ import '[email protected]' with {
 } as k8s
 ```
 
-- **namespace**: Specify the namespace of the provider.
+- **namespace**: Specify the namespace of the extension.
 - **KubeConfig**: Specify a base64 encoded value of the [Kubernetes cluster admin credentials](/rest/api/aks/managed-clusters/list-cluster-admin-credentials).
 
 The following sample shows how to pass `kubeConfig` value from a parent Bicep file:
@@ -81,4 +80,4 @@ From Visual Studio Code, you can import Kubernetes manifest files to create Bice
 
 ## Next steps
 
-- [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep extensibility Kubernetes provider](../../aks/learn/quick-kubernetes-deploy-bicep-extensibility-kubernetes-provider.md)
+- [Quickstart - Deploy Azure applications to Azure Kubernetes Services by using Bicep Kubernetes extension](../../aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension.md)