Merge pull request #295111 from mumian/0221-bcp-201

Add BCP201

Author: v-dirichards

articles/azure-resource-manager/bicep/bicep-core-diagnostics.md

@@ -201,7 +201,7 @@ If you need more information about a particular diagnostic code, select the **Fe
 | <a id='BCP198' />BCP198 | Error | The tag "{badTag}" isn't valid. Valid characters are alphanumeric, ".", "_", or "-" but the tag can't begin with ".", "_", or "-". |
 | <a id='BCP199' />BCP199 | Error | Module path "{badRepository}" exceeds the maximum length of {maxLength} characters. |
 | <a id='BCP200' />BCP200 | Error | The registry "{badRegistry}" exceeds the maximum length of {maxLength} characters. |
-| <a id='BCP201' />BCP201 | Error | Expected a provider specification string of with a valid format at this location. Valid formats are "br:\<providerRegistryHost>/\<providerRepositoryPath>@\<providerVersion>" or "br/\<providerAlias>:\<providerName>@\<providerVersion>". |
+| <a id='BCP201' />[BCP201](./diagnostics/bcp201.md) | Error | Expected an extension specification string. This should either be a relative path, or a valid OCI artifact specification. |
 | <a id='BCP202' />BCP202 | Error | Expected a provider alias name at this location. |
 | <a id='BCP203' />BCP203 | Error | Using provider statements requires enabling EXPERIMENTAL feature "Extensibility". |
 | <a id='BCP204' />BCP204 | Error | Provider namespace "{identifier}" isn't recognized. |

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

@@ -8,7 +8,7 @@ ms.date: 12/06/2024
 
 # Use Bicep extensions
 
-This article describes how to use Bicep extensions.
+Bicep was initially created to enhance the authoring experience compared to Azure Resource Manager JSON templates, simplifying the deployment and management of Azure resources. Bicep extensions build on this foundation, enabling Bicep templates to reference resources beyond the scope of Azure Resource Manager. 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.

articles/azure-resource-manager/bicep/diagnostics/bcp201.md

@@ -0,0 +1,49 @@
+---
+title: BCP201
+description: Expected an extension specification string. This should either be a relative path, or a valid OCI artifact specification.
+ms.topic: reference
+ms.custom: devx-track-bicep
+ms.date: 02/21/2025
+---
+
+# Bicep diagnostic code - BCP201
+
+[Bicep extensions](../bicep-extension.md) enable Bicep files to reference resources beyond the scope of Azure Resource Manager. This diagnostic occurs when there's an invalid `extension` statement.
+
+## Description
+
+Expected an extension specification string. This should either be a relative path, or a valid [OCI artifact](/azure/container-registry/container-registry-image-formats#oci-artifacts) specification.
+
+## Level
+
+Error
+
+## Solution
+
+Remove Use a name of a value.
+
+## Examples
+
+The following example raises the diagnostic because the `extension` statement is invalid:
+
+```bicep
+extension 1
+```
+
+You can fix the diagnostic by using the correct `extension` statement. For example:
+
+```bicep
+@secure()
+param kubeConfig string
+
+extension kubernetes with {
+  namespace: 'default'
+  kubeConfig: kubeConfig
+} as k8s
+```
+
+For more information, see [Bicep extension](../bicep-extension.md).
+
+## Next steps
+
+For more information about Bicep diagnostics, see [Bicep core diagnostics](../bicep-core-diagnostics.md).

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

@@ -697,6 +697,8 @@
       href: diagnostics/bcp170.md
     - name: BCP192
       href: diagnostics/bcp192.md
+    - name: BCP201
+      href: diagnostics/bcp201.md
     - name: BCP238
       href: diagnostics/bcp238.md
     - name: BCP266