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
description: Describes how consumers of Azure Managed Applications approve requests for just-in-time access to a managed application.
4
4
author: MSEvanhi
5
5
ms.topic: conceptual
6
-
ms.date: 06/03/2019
6
+
ms.date: 06/24/2024
7
7
ms.author: evanhi
8
8
---
9
+
9
10
# Configure and approve just-in-time access for Azure Managed Applications
10
11
11
12
As a consumer of a managed application, you might not be comfortable giving the publisher permanent access to the managed resource group. To give you greater control over granting access to managed resources, Azure Managed Applications provides a feature called just-in-time (JIT) access. It enables you to approve when and for how long the publisher has access to the resource group. The publisher can make required updates during that time, but when that time is over, the publisher's access expires.
@@ -45,9 +46,9 @@ This article focuses on the actions consumers take to enable JIT access and appr
45
46
46
47
By default, a managed application with JIT enabled has the following settings:
47
48
48
-
* Approval mode – automatic
49
-
* Maximum access duration – 8 hours
50
-
* Approvers – none
49
+
- Approval mode – automatic
50
+
- Maximum access duration – 8 hours
51
+
- Approvers – none
51
52
52
53
When the approval mode is set to **automatic**, the approvers receive a notification for each request but the request is automatically approved. When set to **manual**, the approvers receive a notification for each request, and one of them must approve it.
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/managed-applications/concepts-built-in-policy.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Deploy associations for managed application using Azure Policy
3
3
description: Learn about deploying associations for a managed application using Azure Policy.
4
4
author: msHich
5
5
ms.topic: conceptual
6
-
ms.date: 06/23/2022
6
+
ms.date: 06/24/2024
7
7
ms.author: hich
8
8
---
9
9
@@ -19,10 +19,10 @@ Deploy associations for a managed application is a built-in policy that associat
19
19
- Resource types to associate - These resource types are the list of resource types to be associated to the managed application. You can associate multiple resource types to a managed application using the same policy.
20
20
- Association name prefix - This string is the prefix to be added to the name of the association resource being created. The default value is `DeployedByPolicy`.
21
21
22
-
The policy uses `DeployIfNotExists` evaluation. It runs after a Resource Provider has handled a create or update resource request of the selected resource type and the evaluation has returned a success status code. After that, the association resource gets deployed using a template deployment.
23
-
For more information on associations, see[Azure Custom Providers resource onboarding](../custom-providers/concepts-resource-onboarding.md)
22
+
The policy uses `DeployIfNotExists` evaluation. It runs after a Resource Provider handled a create or update resource request of the selected resource type and the evaluation returned a success status code. After that, the association resource is deployed using a template deployment.
23
+
For more information on associations, go to[Azure Custom Providers resource onboarding](../custom-providers/concepts-resource-onboarding.md)
24
24
25
-
For more information, see[Deploy associations for a managed application](../../governance/policy/samples/built-in-policies.md#managed-application).
25
+
For more information, go to[Deploy associations for a managed application](../../governance/policy/samples/built-in-policies.md#managed-application).
26
26
27
27
## How to use the deploy associations built-in policy
28
28
@@ -32,18 +32,17 @@ If the managed application needs permissions to the subscription to perform an a
32
32
33
33
### Policy assignment
34
34
35
-
To use the built-in policy, create a policy assignment and assign the Deploy associations for a managed application policy. Once the policy has been assigned successfully,
36
-
the policy will identify non-compliant resources and deploy association for those resources.
35
+
To use the built-in policy, create a policy assignment and assign the deploy associations for a managed application policy. After the policy is assigned successfully, the policy identifies noncompliant resources and deploy associations for those resources.
37
36
38
37
:::image type="content" source="media/concepts-built-in-policy/assign-builtin-policy-managedapp.png" alt-text="Screenshot of Azure portal to create a policy assignment and assign the deploy associations policy.":::
39
38
40
39
## Getting help
41
40
42
-
If you have questions about Azure Custom Resource Providers development, try asking them on [Stack Overflow](https://stackoverflow.com/questions/tagged/azure-custom-providers). A similar question might have already been answered, so check first before posting. Use the tag `azure-custom-providers`.
41
+
If you have questions or need an answer about Azure Custom Resource Providers development, go to [Stack Overflow](https://stackoverflow.com/questions/tagged/azure-custom-providers). Use the tag `azure-custom-providers` when you post a question.
43
42
44
43
## Next steps
45
44
46
-
In this article, you learned about using built-in policy to deploy associations. See these articles to learn more:
45
+
In this article, you learned about using built-in policy to deploy associations. To learn more, review the following articles:
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/managed-applications/concepts-view-definition.md
+41-41Lines changed: 41 additions & 41 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Overview of view definition
3
3
description: Describes the concept of creating view definition for Azure Managed Applications.
4
4
ms.topic: overview
5
-
ms.date: 08/25/2022
5
+
ms.date: 06/24/2024
6
6
---
7
7
8
8
# View definition artifact in Azure Managed Applications
@@ -13,7 +13,7 @@ This article provides an overview of view definition artifact and its capabiliti
13
13
14
14
## View definition artifact
15
15
16
-
The view definition artifact must be named _viewDefinition.json_ and placed at the same level as _createUiDefinition.json_ and _mainTemplate.json_ in the _.zip_ package that creates a managed application definition. To learn how to create the _.zip_ package and publish a managed application definition, see [Publish an Azure Managed Application definition](publish-service-catalog-app.md)
16
+
The view definition artifact must be named _viewDefinition.json_ and placed at the same level as _createUiDefinition.json_ and _mainTemplate.json_ in the _.zip_ package that creates a managed application definition. To learn how to create the _.zip_ package and publish a managed application definition, see [Quickstart: Create and publish an Azure Managed Application definition](publish-service-catalog-app.md)
17
17
18
18
## View definition schema
19
19
@@ -130,11 +130,11 @@ When you provide this view in _viewDefinition.json_, it overrides the default Ov
130
130
}
131
131
```
132
132
133
-
|Property|Required|Description|
133
+
|Property|Required|Description|
134
134
|---------|---------|---------|
135
-
|header|No|The header of the overview page.|
136
-
|description|No|The description of your managed application.|
137
-
|commands|No|The array of more toolbar buttons of the overview page, see [commands](#commands).|
135
+
|`header`| No |The header of the overview page.|
136
+
|`description`| No |The description of your managed application.|
137
+
|`commands`| No |The array of more toolbar buttons of the overview page, see [commands](#commands).|
138
138
139
139
:::image type="content" source="./media/view-definition/overview.png" alt-text="Screenshot shows the Overview for a managed application with a Test Action control to run a demo application.":::
140
140
@@ -171,29 +171,29 @@ The metrics view enables you to collect and aggregate data from your managed app
171
171
}
172
172
```
173
173
174
-
|Property|Required|Description|
174
+
|Property|Required|Description|
175
175
|---------|---------|---------|
176
-
|displayName|No|The displayed title of the view.|
177
-
|version|No|The version of the platform used to render the view.|
178
-
|charts|Yes|The array of charts of the metrics page.|
176
+
|`displayName`|No|The displayed title of the view.|
177
+
|`version`| No |The version of the platform used to render the view.|
178
+
|`charts`|Yes|The array of charts of the metrics page.|
179
179
180
180
### Chart
181
181
182
-
|Property|Required|Description|
182
+
|Property|Required|Description|
183
183
|---------|---------|---------|
184
-
|displayName|Yes|The displayed title of the chart.|
185
-
|chartType|No|The visualization to use for this chart. By default, it uses a line chart. Supported chart types: `Bar, Line, Area, Scatter`.|
186
-
|metrics|Yes|The array of metrics to plot on this chart. To learn more about metrics supported in Azure portal, see [Supported metrics with Azure Monitor](../../azure-monitor/essentials/metrics-supported.md)|
184
+
|`displayName`|Yes|The displayed title of the chart.|
185
+
|`chartType`| No |The visualization to use for this chart. By default, it uses a line chart. Supported chart types: `Bar, Line, Area, Scatter`.|
186
+
|`metrics`|Yes|The array of metrics to plot on this chart. To learn more about metrics supported in Azure portal, see [Supported metrics with Azure Monitor](../../azure-monitor/essentials/metrics-supported.md). |
187
187
188
188
### Metric
189
189
190
-
|Property|Required|Description|
190
+
|Property|Required|Description|
191
191
|---------|---------|---------|
192
-
|name|Yes|The name of the metric.|
193
-
|aggregationType|Yes|The aggregation type to use for this metric. Supported aggregation types: `none, sum, min, max, avg, unique, percentile, count`|
194
-
|namespace|No| More information to use when determining the correct metrics provider.|
195
-
|resourceTagFilter|No|The resource tags array (will be separated with `or` word) for which metrics would be displayed. Applies on top of resource type filter.|
196
-
|resourceType|Yes|The resource type for which metrics would be displayed.|
192
+
|`name`|Yes|The name of the metric.|
193
+
|`aggregationType`|Yes|The aggregation type to use for this metric. Supported aggregation types: `none, sum, min, max, avg, unique, percentile, count`|
194
+
|`namespace`| No | More information to use when determining the correct metrics provider.|
195
+
|`resourceTagFilter`| No |The resource tags array is separated with an `or` word for which metrics would be displayed. Applies on top of resource type filter.|
196
+
|`resourceType`|Yes|The resource type for which metrics would be displayed.|
197
197
198
198
:::image type="content" source="./media/view-definition/metrics.png" alt-text="Screenshot shows a Monitoring page called This is my metrics view for a managed application.":::
199
199
@@ -203,7 +203,7 @@ The metrics view enables you to collect and aggregate data from your managed app
203
203
204
204
You can define multiple views of this type. Each view represents a **unique** custom resource type from the custom provider you defined in _mainTemplate.json_. For an introduction to custom providers, see [Azure Custom Providers Preview overview](../custom-providers/overview.md).
205
205
206
-
In this view you can perform GET, PUT, DELETE and POST operations for your custom resource type. POST operations could be global custom actions or custom actions in a context of your custom resource type.
206
+
In this view you can perform GET, PUT, DELETE, and POST operations for your custom resource type. POST operations could be global custom actions or custom actions in a context of your custom resource type.
207
207
208
208
```json
209
209
{
@@ -241,15 +241,15 @@ In this view you can perform GET, PUT, DELETE and POST operations for your custo
241
241
}
242
242
```
243
243
244
-
|Property|Required|Description|
244
+
|Property|Required|Description|
245
245
|---------|---------|---------|
246
-
|displayName|Yes|The displayed title of the view. The title should be **unique** for each CustomResources view in your _viewDefinition.json_.|
247
-
|version|No|The version of the platform used to render the view.|
248
-
|resourceType|Yes|The custom resource type. Must be a **unique** custom resource type of your custom provider.|
249
-
|icon|No|The icon of the view. List of example icons is defined in [JSON Schema](https://schema.management.azure.com/schemas/viewdefinition/0.0.1-preview/ViewDefinition.json#).|
250
-
|createUIDefinition|No|Create UI Definition schema for create custom resource command. For an introduction to creating UI definitions, see [Getting started with CreateUiDefinition](create-uidefinition-overview.md)|
251
-
|commands|No|The array of more toolbar buttons of the CustomResources view, see [commands](#commands).|
252
-
|columns|No|The array of columns of the custom resource. If not defined the `name` column will be shown by default. The column must have `"key"` and `"displayName"`. For key, provide the key of the property to display in a view. If nested, use dot as delimiter, for example, `"key": "name"` or `"key": "properties.property1"`. For display name, provide the display name of the property to display in a view. You can also provide an `"optional"` property. When set to true, the column is hidden in a view by default.|
246
+
|`displayName`|Yes|The displayed title of the view. The title should be **unique** for each CustomResources view in your _viewDefinition.json_.|
247
+
|`version`| No |The version of the platform used to render the view.|
248
+
|`resourceType`|Yes|The custom resource type. Must be a **unique** custom resource type of your custom provider.|
249
+
|`icon`| No |The icon of the view. List of example icons is defined in [JSON Schema](https://schema.management.azure.com/schemas/viewdefinition/0.0.1-preview/ViewDefinition.json#).|
250
+
|`createUIDefinition`| No |Create UI Definition schema for create custom resource command. For an introduction to creating UI definitions, see [Getting started with CreateUiDefinition](create-uidefinition-overview.md). |
251
+
|`commands`|No|The array of more toolbar buttons of the CustomResources view, see [commands](#commands).|
252
+
|`columns`| No |The array of columns of the custom resource. If not defined the `name` column is shown by default. The column must have `"key"` and `"displayName"`. For key, provide the key of the property to display in a view. If nested, use dot as delimiter, for example, `"key": "name"` or `"key": "properties.property1"`. For display name, provide the display name of the property to display in a view. You can also provide an `"optional"` property. When set to true, the column is hidden in a view by default.|
253
253
254
254
:::image type="content" source="./media/view-definition/customresources.png" alt-text="Screenshot shows a Resources page called Test custom resource type and the control Custom Context Action.":::
255
255
@@ -270,20 +270,20 @@ The `commands` property is an array of more toolbar buttons that are displayed o
270
270
}
271
271
```
272
272
273
-
|Property|Required|Description|
273
+
|Property|Required|Description|
274
274
|---------|---------|---------|
275
-
|displayName|Yes|The displayed name of the command button.|
276
-
|path|Yes| Must be a custom provider action name. The action must be defined in _mainTemplate.json_. <br><br> Doesn't accept dynamic values like a URI that's output from _mainTemplate.json_. |
277
-
|icon|No|The icon of the command button. List of example icons is defined in [JSON Schema](https://schema.management.azure.com/schemas/viewdefinition/0.0.1-preview/ViewDefinition.json#).|
278
-
|createUIDefinition|No|Create UI Definition schema for command. For an introduction to creating UI definitions, see [Getting started with CreateUiDefinition](create-uidefinition-overview.md).|
275
+
|`displayName`|Yes|The displayed name of the command button.|
276
+
|`path`|Yes| Must be a custom provider action name. The action must be defined in _mainTemplate.json_. <br><br> Doesn't accept dynamic values like a URI that's output from _mainTemplate.json_. |
277
+
|`icon`| No |The icon of the command button. List of example icons is defined in [JSON Schema](https://schema.management.azure.com/schemas/viewdefinition/0.0.1-preview/ViewDefinition.json#).|
278
+
|`createUIDefinition`|No|Create UI Definition schema for command. For an introduction to creating UI definitions, see [Getting started with CreateUiDefinition](create-uidefinition-overview.md).|
279
279
280
280
## Associations
281
281
282
282
`"kind": "Associations"`
283
283
284
284
You can define multiple views of this type. This view allows you to link existing resources to the managed application through the custom provider you defined in _mainTemplate.json_. For an introduction to custom providers, see [Azure Custom Providers Preview overview](../custom-providers/overview.md).
285
285
286
-
In this view, you can extend existing Azure resources based on the `targetResourceType`. When a resource is selected, it will create an onboarding request to the **public** custom provider, which can apply a side effect to the resource.
286
+
In this view, you can extend existing Azure resources based on the `targetResourceType`. When a resource is selected, it creates an onboarding request to the **public** custom provider, which can apply a side effect to the resource.
287
287
288
288
```json
289
289
{
@@ -297,16 +297,16 @@ In this view, you can extend existing Azure resources based on the `targetResour
297
297
}
298
298
```
299
299
300
-
|Property|Required|Description|
300
+
|Property|Required|Description|
301
301
|---------|---------|---------|
302
-
|displayName|Yes|The displayed title of the view. The title should be **unique** for each Associations view in your _viewDefinition.json_.|
303
-
|version|No|The version of the platform used to render the view.|
304
-
|targetResourceType|Yes|The target resource type. This resource type will be displayed for resource onboarding.|
305
-
|createUIDefinition|No|Create UI Definition schema for create association resource command. For an introduction to creating UI definitions, see [Getting started with CreateUiDefinition](create-uidefinition-overview.md)|
302
+
|`displayName`|Yes|The displayed title of the view. The title should be unique for each Associations view in your _viewDefinition.json_.|
303
+
|`version`| No |The version of the platform used to render the view.|
304
+
|`targetResourceType`|Yes|The target resource type. This resource type is displayed for resource onboarding.|
305
+
|`createUIDefinition`| No |Create UI Definition schema for create association resource command. For an introduction to creating UI definitions, see [Getting started with CreateUiDefinition](create-uidefinition-overview.md). |
306
306
307
307
## Looking for help
308
308
309
-
If you have questions about Azure Managed Applications, try asking on [Stack Overflow](https://stackoverflow.com/questions/tagged/azure-managed-app). A similar question may have already been asked and answered, so check first before posting. Add the tag `azure-managed-app`to get a fast response!
309
+
If you have questions or need an answer about Azure Managed Applications, try asking on [Stack Overflow](https://stackoverflow.com/questions/tagged/azure-managed-app). Use the tag `azure-managed-app`when you post a question.
0 commit comments