From b95e917a10a13a38b1e7b526624183aca90523ca Mon Sep 17 00:00:00 2001 From: Teemu Tapanila Date: Thu, 21 Mar 2024 11:02:59 +0200 Subject: [PATCH 1/2] Update provider syntax in getting started documentation --- docs/getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started.md b/docs/getting-started.md index b26c3e6..72b155a 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -23,7 +23,7 @@ To get the benefit of intellisense and auto-complete for the Microsoft Graph Bic When you create a Bicep template, add the following statement, to make Microsoft Graph Bicep types readily accessible to the template. ```bicep -provider 'microsoftGraph@1.0.0' +provider microsoftGraph ``` Now, when creating a Bicep resource, the available Microsoft.Graph resource types will show up. From 5c642c8cd812d85e43a13bafb0c48b06df130a23 Mon Sep 17 00:00:00 2001 From: Teemu Tapanila Date: Thu, 21 Mar 2024 11:04:23 +0200 Subject: [PATCH 2/2] Update provider syntax in use existing resources documentation --- docs/use-existing-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-existing-resources.md b/docs/use-existing-resources.md index 9acd381..f4d91c2 100644 --- a/docs/use-existing-resources.md +++ b/docs/use-existing-resources.md @@ -54,7 +54,7 @@ Content-type: application/json Once the group resource is "back-filled", it can be referenced by its unique name, using the `existing` keyword in a Bicep template: ```Bicep -import 'microsoftGraph@1.0.0' +provider microsoftGraph @description('Group to use') param groupName string = 'TestGroup-2023-10-10'