You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/custom-providers/concepts-built-in-policy.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ If the custom resource provider needs permissions to the scope of the policy to
30
30
### Policy assignment
31
31
To use the built-in policy, create a policy assignment and assign the Deploy associations for a custom resource provider policy. The policy will then identify non-compliant resources and deploy association for those resources.
:::image type="content" source="media/concepts-built-in-policy/assign-builtin-policy-customprovider.png" alt-text="Screenshot of the Assign built-in policy for custom resource provider in Azure portal.":::
To deploy the template from the Azure portal, select the **Deploy to Azure** button.
81
81
82
-
[](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-docs-json-samples%2Fmaster%2Fcustom-providers%2Fcustomprovider.json)
82
+
:::image type="content" source="../../media/template-deployments/deploy-to-azure.svg" alt-text="Illustration of the Deploy to Azure button." link="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-docs-json-samples%2Fmaster%2Fcustom-providers%2Fcustomprovider.json":::
83
83
84
84
## View custom resource provider and resource
85
85
86
86
In the portal, the custom resource provider is a hidden resource type. To confirm that the resource provider was deployed, go to the resource group and select **Show hidden types**.
87
87
88
-
:::image type="content" source="./media/create-custom-provider/show-hidden.png" alt-text="Screenshot that shows hidden resource types and resources deployed in Azure.":::
88
+
:::image type="content" source="./media/create-custom-provider/show-hidden.png" alt-text="Screenshot of Azure portal displaying hidden resource types and resources deployed in a resource group.":::
89
89
90
90
To see the custom resource that you deployed, use the `GET` operation on your resource type. The resource type `Microsoft.CustomProviders/resourceProviders/users` shown in the JSON response includes the resource that was created by the template.
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/custom-providers/tutorial-custom-providers-function-setup.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ To install the Azure Table storage bindings:
31
31
1. In the **Table name** box, enter *myCustomResources*.
32
32
1. Select **Save** to save the updated input parameter.
33
33
34
-
:::image type="content" source="./media/tutorial-custom-providers-function-setup/azure-functions-table-bindings.png" alt-text="Screenshot of the custom resource provider overview showing table bindings.":::
34
+
:::image type="content" source="./media/tutorial-custom-providers-function-setup/azure-functions-table-bindings.png" alt-text="Screenshot of the Azure Functions Integrate tab displaying Azure Table Storage bindings configuration.":::
35
35
36
36
## Update RESTful HTTP methods
37
37
@@ -40,7 +40,7 @@ To set up the Azure function to include the custom resource provider RESTful req
40
40
1. Go to the **Integrate** tab for the `HttpTrigger`.
41
41
1. Under **Selected HTTP methods**, select **GET**, **POST**, **DELETE**, and **PUT**.
42
42
43
-
:::image type="content" source="./media/tutorial-custom-providers-function-setup/azure-functions-http-methods.png" alt-text="Screenshot of the custom resource provider overview showing HTTP methods.":::
43
+
:::image type="content" source="./media/tutorial-custom-providers-function-setup/azure-functions-http-methods.png" alt-text="Screenshot of the Azure Functions Integrate tab displaying the selection of RESTful HTTP methods.":::
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/custom-providers/tutorial-resource-onboarding.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -208,25 +208,25 @@ Let's deploy the custom resource provider infrastructure. Either copy, save, and
208
208
209
209
2. Search for **templates** in **All Services** or by using the main search box:
210
210
211
-

211
+
:::image type="content" source="media/tutorial-resource-onboarding/templates.png" alt-text="Screenshot of the search bar in Azure portal with 'templates' entered as the search query.":::
:::image type="content" source="media/tutorial-resource-onboarding/templatesadd.png" alt-text="Screenshot of the Templates pane in Azure portal with the Add button highlighted.":::
216
216
217
217
4. Under **General**, enter a *Name* and *Description* for the new template:
218
218
219
-

219
+
:::image type="content" source="media/tutorial-resource-onboarding/templatesdescription.png" alt-text="Screenshot of the General section in Azure portal where the user enters a Name and Description for the new template.":::
220
220
221
221
5. Create the Resource Manager template by copying in the JSON template from the "Get started with resource onboarding" section of this article:
222
222
223
-

223
+
:::image type="content" source="media/tutorial-resource-onboarding/templatesarmtemplate.png" alt-text="Screenshot of the Azure portal where the user pastes the JSON template into the ARM Template section.":::
224
224
225
225
6. Select **Add** to create the template. If the new template doesn't appear, select **Refresh**.
226
226
227
227
7. Select the newly created template and then select **Deploy**:
228
228
229
-

229
+
:::image type="content" source="media/tutorial-resource-onboarding/templateselectspecific.png" alt-text="Screenshot of the Azure portal showing the newly created template with the Deploy button highlighted.":::
230
230
231
231
8. Enter the settings for the required fields and then select the subscription and resource group. You can leave the **Custom Resource Provider Id** box empty.
232
232
@@ -240,43 +240,43 @@ Let's deploy the custom resource provider infrastructure. Either copy, save, and
:::image type="content" source="media/tutorial-resource-onboarding/templatescustomprovider.png" alt-text="Screenshot of the Azure portal displaying the template parameters input fields for the custom resource provider deployment.":::
244
244
245
245
9. Go to the deployment and wait for it to finish. You should see something like the following screenshot. You should see the new association resource as an output:
:::image type="content" source="media/tutorial-resource-onboarding/customproviderdeployment.png" alt-text="Screenshot of the Azure portal showing a successful deployment with the new association resource as an output.":::
248
248
249
249
Here's the resource group, with **Show hidden types** selected:
:::image type="content" source="media/tutorial-resource-onboarding/showhidden.png" alt-text="Screenshot of the resource group in Azure portal with Show hidden types selected, displaying the custom resource provider deployment.":::
252
252
253
253
10. Explore the logic app **Runs history** tab to see the calls for the association create:
:::image type="content" source="media/tutorial-resource-onboarding/logicapprun.png" alt-text="Screenshot of the Logic app Runs history tab in Azure portal showing the calls for the association create.":::
256
256
257
257
## Deploy additional associations
258
258
259
259
After you have the custom resource provider infrastructure set up, you can easily deploy more associations. The resource group for additional associations doesn't have to be the same as the resource group where you deployed the custom resource provider infrastructure. To create an association, you need to have Microsoft.CustomProviders/resourceproviders/write permissions on the specified Custom Resource Provider ID.
260
260
261
261
1. Go to the custom resource provider **Microsoft.CustomProviders/resourceProviders** resource in the resource group of the previous deployment. You need to select the **Show hidden types** check box:
262
262
263
-

263
+
:::image type="content" source="media/tutorial-resource-onboarding/showhidden.png" alt-text="Screenshot of the Azure portal displaying the custom resource provider resource in the resource group with Show hidden types selected.":::
264
264
265
265
2. Copy the Resource ID property of the custom resource provider.
266
266
267
267
3. Search for *templates* in **All Services** or by using the main search box:
268
268
269
-

269
+
:::image type="content" source="media/tutorial-resource-onboarding/templates.png" alt-text="Screenshot of the search bar in Azure portal with 'templates' entered as the search query.":::
270
270
271
271
4. Select the previously created template and then select **Deploy**:
272
272
273
-

273
+
:::image type="content" source="media/tutorial-resource-onboarding/templateselectspecific.png" alt-text="Screenshot of the Azure portal showing the previously created template with the Deploy button highlighted.":::
274
274
275
275
5. Enter the settings for the required fields and then select the subscription and a different resource group. For the **Custom Resource Provider Id** setting, enter the Resource ID that you copied from the custom resource provider that you deployed earlier.
276
276
277
277
6. Go to the deployment and wait for it to finish. It should now deploy only the new associations resource:
:::image type="content" source="media/tutorial-resource-onboarding/createdassociationresource.png" alt-text="Screenshot of the Azure portal displaying the successful deployment of the new associations resource.":::
280
280
281
281
You can go back to the logic app **Run history** and see that another call was made to the logic app. You can update the logic app to augment additional functionality for each created association.
0 commit comments