Merge pull request #291612 from mumian/1206-rename-import-extension

Rename import to extension

Author: v-shils

articles/azure-resource-manager/bicep/bicep-extension.md

@@ -0,0 +1,38 @@
+---
+title: Use extensions in Bicep
+description: This article describes how to use Bicep extensions.
+ms.topic: conceptual
+ms.custom: devx-track-bicep
+ms.date: 12/06/2024
+---
+
+# Use Bicep extensions
+
+This article describes how to use Bicep extensions.
+
+> [!NOTE]
+> The experimental feature `extensibility` must be enabled from the [Bicep config file](./bicep-config.md#enable-experimental-features) to use this feature.
+
+The syntax for importing Bicep extensions is:
+
+```bicep
+extionsion <extension-name>
+```
+
+The syntax for importing Bicep extensions, which require configuration is:
+
+```bicep
+extension <extension-name> with {
+  <extension-properties>
+}
+```
+
+For examples, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md) and [Microsoft Graph extension](https://aka.ms/graphbicep).
+
+## Related content
+
+- To learn about Bicep data types, see [Data types](./data-types.md).
+- To learn about Bicep functions, see [Bicep functions](./bicep-functions.md).
+- To learn how to use the Bicep 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 the Bicep Kubernetes extension](/azure/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension).
+- To learn Microsoft Graph extension, see [Microsoft Graph extension](https://aka.ms/graphbicep).

articles/azure-resource-manager/bicep/bicep-import.md

@@ -8,7 +8,7 @@ ms.date: 12/06/2024
 
 # Imports in Bicep
 
-This article describes the syntax you use to export and import shared functionality and namespaces for Bicep extensions. Using compile-time imports automatically enables [language version 2.0](../templates/syntax.md#languageversion-20) code generation.
+This article describes the syntax you use to export and import shared functionality and namespaces. Using compile-time imports automatically enables [language version 2.0](../templates/syntax.md#languageversion-20) code generation.
 
 ## Export variables, types, and functions
 
@@ -80,10 +80,7 @@ output greeting string = sayHello('Bicep user')
 output exampleObject myImports.myObjectType = exampleObject
 ```
 
-## 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.
+## Import namespaces
 
 The syntax for importing namespaces is:
 
@@ -94,22 +91,6 @@ import '[email protected]'
 
 Both `az` and `sys` are Bicep built-in namespaces. They're 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 extensions is:
-
-```bicep
-import '<extension-name>@<extension-version>'
-```
-
-The syntax for importing Bicep extensions, which require configuration is:
-
-```bicep
-import '<extension-name>@<extension-version>' with {
-  <extension-properties>
-}
-```
-
-For an example, see [Bicep Kubernetes extension](./bicep-kubernetes-extension.md).
-
 ## Related content
 
 - To learn about the Bicep data types, see [Data types](./data-types.md).

articles/azure-resource-manager/bicep/bicep-kubernetes-extension.md

@@ -40,15 +40,15 @@ This preview feature can be enabled by configuring the [bicepconfig.json](./bice
 ## 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 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.
+To import the Kubernetes extension, use the [extension statement](./bicep-extension.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 extension:
 
 ```bicep
 @secure()
 param kubeConfig string
 
-import 'kubernetes@1.0.0' with {
+extension kubernetes with {
   namespace: 'default'
   kubeConfig: kubeConfig
 } as k8s
@@ -60,7 +60,7 @@ import '[email protected]' with {
 The following sample shows how to pass `kubeConfig` value from a parent Bicep file:
 
 ```bicep
-resource aks 'Microsoft.ContainerService/managedClusters@2024-02-01' existing = {
+resource aks 'Microsoft.ContainerService/managedClusters@2024-08-01' existing = {
   name: 'demoAKSCluster'
 }
 

articles/azure-resource-manager/bicep/toc.yml

@@ -262,22 +262,31 @@
   - name: Data types
     href: data-types.md
     displayName: supported types,arrays,booleans,integers,objects,strings,secure,interpolation
-  - name: User-defined data types (type)
-    displayName: custom
-    href: user-defined-data-types.md
-  - name: User-defined functions (func)
-    displayName: custom
-    href: user-defined-functions.md
   - name: Parameters (param)
     href: parameters.md
     displayName: decorators,secure,objects,constraints
   - name: Variables (var)
     href: variables.md
     displayName: configuration
-  - name: Import (import)
-    href: bicep-import.md
   - name: Resources (resource)
     href: resource-declaration.md
+  - name: Outputs (output)
+    href: outputs.md
+    displayName: dynamic number of outputs,modules
+  - name: Modules (module)
+    href: modules.md
+    displayName: scopes,consume,registry,module registry,private module registry,public module registry,avm,azure verified modules 
+  - name: Using (using)
+    displayName: avm,azure verified modules 
+    href: bicep-using.md
+  - name: Import (import)
+    href: bicep-import.md
+  - name: User-defined data types (type)
+    displayName: custom
+    href: user-defined-data-types.md
+  - name: User-defined functions (func)
+    displayName: custom
+    href: user-defined-functions.md
   - name: Existing resources (existing)
     href: existing-resource.md
   - name: Child resources (parent)
@@ -287,20 +296,13 @@
     href: scope-extension-resources.md
   - name: Dependencies (dependsOn)
     href: resource-dependencies.md
-  - name: Modules (module)
-    href: modules.md
-    displayName: scopes,consume,registry,module registry,private module registry,public module registry,avm,azure verified modules 
-  - name: Outputs (output)
-    href: outputs.md
-    displayName: dynamic number of outputs,modules
   - name: Loops (for)
     href: loops.md
     displayName: multiple
   - name: Conditions (if)
     href: conditional-resource-deployment.md
-  - name: Using (using)
-    displayName: avm,azure verified modules 
-    href: bicep-using.md
+  - name: Extension (extension)
+    href: bicep-extension.md
   - name: Scopes (targetScope)
     items:
     - name: Resource group