Skip to content

Commit 4224c21

Browse files
davidsmatlakdavidsmatlak
committed
freshness updates
1 parent a04a80d commit 4224c21

8 files changed

+37
-37
lines changed

‎articles/azure-resource-manager/managed-applications/deploy-bicep-definition.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use Bicep to deploy an Azure Managed Application definition
33
description: Describes how to use Bicep to deploy an Azure Managed Application definition from your service catalog.
44
ms.topic: quickstart
55
ms.custom: devx-track-azurepowershell, devx-track-bicep, devx-track-azurecli
6-
ms.date: 05/29/2024
6+
ms.date: 06/24/2024
77
---
88

99
# Quickstart: Use Bicep to deploy an Azure Managed Application definition

‎articles/azure-resource-manager/managed-applications/deploy-service-catalog-quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Deploy a service catalog managed application
33
description: Describes how to deploy a service catalog's managed application for an Azure Managed Application using Azure PowerShell, Azure CLI, or Azure portal.
44
ms.topic: quickstart
5-
ms.date: 05/28/2024
5+
ms.date: 06/24/2024
66
ms.custom: engagement-fy23, devx-track-azurecli, devx-track-azurepowershell
77
---
88

‎articles/azure-resource-manager/managed-applications/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ metadata:
1010
ms.topic: landing-page
1111
author: davidsmatlak
1212
ms.author: davidsmatlak
13-
ms.date: 05/29/2024
13+
ms.date: 06/24/2024
1414

1515
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
1616

‎articles/azure-resource-manager/managed-applications/publish-bicep-definition.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use Bicep to create and publish an Azure Managed Application definition
33
description: Describes how to use Bicep to create and publish an Azure Managed Application definition in your service catalog.
44
ms.topic: quickstart
55
ms.custom: devx-track-azurecli, devx-track-azurepowershell, devx-track-bicep
6-
ms.date: 05/29/2024
6+
ms.date: 06/24/2024
77
---
88

99
# Quickstart: Use Bicep to create and publish an Azure Managed Application definition

‎articles/azure-resource-manager/managed-applications/publish-managed-identity.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,14 @@
22
title: Managed app with managed identity
33
description: Configure an Azure Managed Application with managed identity for linking to existing resources, managing Azure resources, and providing operational identity for Activity Log.
44
ms.topic: conceptual
5-
ms.date: 07/19/2023
5+
ms.date: 06/24/2024
66
ms.custom: subject-rbac-steps
77
---
88

99
# Azure Managed Application with managed identity
1010

1111
> [!NOTE]
12-
> Managed identity support for Azure Managed Applications is currently in preview. Please use the 2018-09-01-preview api version to utilize managed identity.
12+
> Managed identity support for Azure Managed Applications is currently in preview. Use the 2018-09-01-preview api version to utilize managed identity.
1313
1414
Learn how to configure a managed application to contain a managed identity. A managed identity can be used to allow the customer to grant the managed application access to existing resources. The Azure platform manages the identity and doesn't require you to provision or rotate any secrets. For more about managed identities in Microsoft Entra ID, see [Managed identities for Azure resources](../../active-directory/managed-identities-azure-resources/overview.md).
1515

@@ -305,7 +305,7 @@ Once the managed application package is created, the managed application can be
305305

306306
## Accessing the managed identity token
307307

308-
The token of the managed application can now be accessed through the `listTokens` api from the publisher tenant. An example request might look like:
308+
The token of the managed application can now be accessed through the `listTokens` API from the publisher tenant. An example request might look like:
309309

310310
```http
311311
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Solutions/applications/{applicationName}/listTokens?api-version=2018-09-01-preview HTTP/1.1

‎articles/azure-resource-manager/managed-applications/publish-notifications.md

Lines changed: 28 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Azure managed applications with notifications
33
description: Configure an Azure managed application with webhook endpoints to receive notifications about creates, updates, deletes, and errors on the managed application instances.
44
ms.topic: how-to
5-
ms.date: 08/18/2022
5+
ms.date: 06/24/2024
66
---
77

88
# Azure managed applications with notifications
@@ -69,27 +69,27 @@ For more information, see [Create an Azure application offer](../../marketplace/
6969

7070
The following table describes all the possible combinations of `eventType` and `provisioningState` and their triggers:
7171

72-
EventType | ProvisioningState | Trigger for notification
73-
---|---|---
74-
PUT | Accepted | Managed resource group has been created and projected successfully after application PUT (before the deployment inside the managed resource group is kicked off).
75-
PUT | Succeeded | Full provisioning of the managed application succeeded after a PUT.
76-
PUT | Failed | Failure of PUT of application instance provisioning at any point.
77-
PATCH | Succeeded | After a successful PATCH on the managed application instance to update tags, JIT access policy, or managed identity.
78-
DELETE | Deleting | As soon as the user initiates a DELETE of a managed app instance.
79-
DELETE | Deleted | After the full and successful deletion of the managed application.
80-
DELETE | Failed | After any error during the deprovisioning process that blocks the deletion.
72+
| EventType | ProvisioningState | Trigger for notification |
73+
| --- | --- | --- |
74+
| PUT | Accepted | Managed resource group was created and projected successfully after application PUT (before the deployment inside the managed resource group is kicked off). |
75+
| PUT | Succeeded | Full provisioning of the managed application succeeded after a PUT. |
76+
| PUT | Failed | Failure of PUT of application instance provisioning at any point. |
77+
| PATCH | Succeeded | After a successful PATCH on the managed application instance to update tags, just-in-time (JIT) access policy, or managed identity. |
78+
| DELETE | Deleting | As soon as the user initiates a DELETE of a managed app instance. |
79+
| DELETE | Deleted | After the full and successful deletion of the managed application. |
80+
| DELETE | Failed | After any error during the deprovisioning process that blocks the deletion. |
8181

8282
## Notification schema
8383

84-
When you create your webhook endpoint to handle notifications, you'll need to parse the payload to get important properties to then act upon the notification. Service catalog and Azure Marketplace managed application notifications provide many of the same properties, but there are some differences. The `applicationDefinitionId` property only applies to service catalog. The `billingDetails` and `plan` properties only apply to Azure Marketplace.
84+
When you create your webhook endpoint to handle notifications, you need to parse the payload to get important properties to then act upon the notification. Service catalog and Azure Marketplace managed application notifications provide many of the same properties, but there are some differences. The `applicationDefinitionId` property only applies to service catalog. The `billingDetails` and `plan` properties only apply to Azure Marketplace.
8585

8686
Azure appends `/resource` to the notification endpoint URI you provided in the managed application definition. The webhook endpoint must be able to handle notifications on the `/resource` URI. For example, if you provided a notification endpoint URI like `https://fabrikam.com` then the webhook endpoint URI is `https://fabrikam.com/resource`.
8787

8888
### Service catalog application notification schema
8989

9090
The following sample shows a service catalog notification after the successful provisioning of a managed application instance.
9191

92-
``` HTTP
92+
```HTTP
9393
POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_parameter_value} HTTP/1.1
9494

9595
{
@@ -101,9 +101,9 @@ POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_paramet
101101
}
102102
```
103103

104-
If the provisioning fails, a notification with the error details will be sent to the specified endpoint.
104+
If provisioning fails, a notification with the error details is sent to the specified endpoint.
105105

106-
``` HTTP
106+
```HTTP
107107
POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_parameter_value} HTTP/1.1
108108
109109
{
@@ -129,7 +129,7 @@ POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_paramet
129129

130130
The following sample shows a service catalog notification after the successful provisioning of a managed application instance.
131131

132-
``` HTTP
132+
```HTTP
133133
POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_parameter_value} HTTP/1.1
134134
135135
{
@@ -149,9 +149,9 @@ POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_paramet
149149
}
150150
```
151151

152-
If the provisioning fails, a notification with the error details will be sent to the specified endpoint.
152+
If provisioning fails, a notification with the error details is sent to the specified endpoint.
153153

154-
``` HTTP
154+
```HTTP
155155
POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_parameter_value} HTTP/1.1
156156
157157
{
@@ -181,16 +181,16 @@ POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_paramet
181181
}
182182
```
183183

184-
Property | Description
185-
---|---
186-
`eventType` | The type of event that triggered the notification. (For example, PUT, PATCH, DELETE.)
187-
`applicationId` | The fully qualified resource identifier of the managed application for which the notification was triggered.
188-
`eventTime` | The timestamp of the event that triggered the notification. (Date and time in UTC ISO 8601 format.)
189-
`provisioningState` | The provisioning state of the managed application instance. For example, Succeeded, Failed, Deleting, Deleted.
190-
`applicationDefinitionId` | _Specified only for service catalog managed applications_. Represents the fully qualified resource identifier of the application definition for which the managed application instance was provisioned.
191-
`billingDetails` | _Specified only for Azure Marketplace managed applications_. The billing details of the managed application instance. Contains the `resourceUsageId` that you can use to query Azure Marketplace for usage details.
192-
`plan` | _Specified only for Azure Marketplace managed applications_. Represents the publisher, offer, SKU, and version of the managed application instance.
193-
`error` | _Specified only when the provisioningState is Failed_. Contains the error code, message, and details of the issue that caused the failure.
184+
| Property | Description |
185+
| --- | --- |
186+
| `eventType` | The type of event that triggered the notification. For example, PUT, PATCH, DELETE. |
187+
| `applicationId` | The fully qualified resource identifier of the managed application for which the notification was triggered. |
188+
| `eventTime` | The timestamp of the event that triggered the notification. Date and time in UTC ISO 8601 format. |
189+
| `provisioningState` | The provisioning state of the managed application instance. For example, Succeeded, Failed, Deleting, Deleted. |
190+
| `applicationDefinitionId` | _Specified only for service catalog managed applications_. Represents the fully qualified resource identifier of the application definition for which the managed application instance was provisioned. |
191+
| `billingDetails` | _Specified only for Azure Marketplace managed applications_. The billing details of the managed application instance. Contains the `resourceUsageId` that you can use to query Azure Marketplace for usage details. |
192+
| `plan` | _Specified only for Azure Marketplace managed applications_. Represents the publisher, offer, SKU, and version of the managed application instance. |
193+
| `error` | _Specified only when the provisioningState is Failed_. Contains the error code, message, and details of the issue that caused the failure. |
194194

195195
## Endpoint authentication
196196

@@ -201,4 +201,4 @@ To secure the webhook endpoint and ensure the authenticity of the notification:
201201

202202
## Notification retries
203203

204-
The managed application notification service expects a `200 OK` response from the webhook endpoint to the notification. The notification service will retry if the webhook endpoint returns an HTTP error code greater than or equal to 500, it returns an error code of 429, or if the endpoint is temporarily unreachable. If the webhook endpoint doesn't become available within 10 hours, the notification message will be dropped, and the retries will stop.
204+
The managed application notification service expects a `200 OK` response from the webhook endpoint to the notification. The notification service retries if the webhook endpoint returns an HTTP error code greater than or equal to 500, it returns an error code of 429, or if the endpoint is temporarily unreachable. If the webhook endpoint doesn't become available within 10 hours, the notification message is dropped, and the retries stop.

‎articles/azure-resource-manager/managed-applications/publish-service-catalog-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create and publish Azure Managed Application in service catalog
33
description: Describes how to create and publish an Azure Managed Application in your service catalog using Azure PowerShell, Azure CLI, or Azure portal.
44
ms.topic: quickstart
55
ms.custom: subject-armqs, devx-track-azurecli, devx-track-azurepowershell, subject-rbac-steps, mode-api, mode-arm, devx-track-arm-template, engagement-fy23
6-
ms.date: 05/29/2024
6+
ms.date: 06/24/2024
77
---
88

99
# Quickstart: Create and publish an Azure Managed Application definition

‎articles/azure-resource-manager/managed-applications/publish-service-catalog-bring-your-own-storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Bring your own storage to create and publish an Azure Managed Application
33
description: Describes how to bring your own storage to create and publish an Azure Managed Application definition in your service catalog.
44
ms.topic: quickstart
55
ms.custom: subject-armqs, devx-track-azurecli, devx-track-azurepowershell, subject-rbac-steps, mode-api, mode-arm, devx-track-arm-template, engagement-fy23
6-
ms.date: 05/29/2024
6+
ms.date: 06/24/2024
77
---
88

99
# Quickstart: Bring your own storage to create and publish an Azure Managed Application definition

0 commit comments

Comments
 (0)