Merge pull request #279107 from davidsmatlak/ds-updates-ama-20240624-4

Freshness updates for Managed Apps content

Author: prmerger-automator[bot]

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

@@ -3,7 +3,7 @@ title: Use Bicep to deploy an Azure Managed Application definition
 description: Describes how to use Bicep to deploy an Azure Managed Application definition from your service catalog.
 ms.topic: quickstart
 ms.custom: devx-track-azurepowershell, devx-track-bicep, devx-track-azurecli
-ms.date: 05/29/2024
+ms.date: 06/24/2024
 ---
 
 # Quickstart: Use Bicep to deploy an Azure Managed Application definition

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

@@ -2,7 +2,7 @@
 title: Deploy a service catalog managed application
 description: Describes how to deploy a service catalog's managed application for an Azure Managed Application using Azure PowerShell, Azure CLI, or Azure portal.
 ms.topic: quickstart
-ms.date: 05/28/2024
+ms.date: 06/24/2024
 ms.custom: engagement-fy23, devx-track-azurecli, devx-track-azurepowershell
 ---
 

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

@@ -10,7 +10,7 @@ metadata:
   ms.topic: landing-page
   author: davidsmatlak
   ms.author: davidsmatlak
-  ms.date: 05/29/2024
+  ms.date: 06/24/2024
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 

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

@@ -3,7 +3,7 @@ title: Use Bicep to create and publish an Azure Managed Application definition
 description: Describes how to use Bicep to create and publish an Azure Managed Application definition in your service catalog.
 ms.topic: quickstart
 ms.custom: devx-track-azurecli, devx-track-azurepowershell, devx-track-bicep
-ms.date: 05/29/2024
+ms.date: 06/24/2024
 ---
 
 # Quickstart: Use Bicep to create and publish an Azure Managed Application definition

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

@@ -2,14 +2,14 @@
 title: Managed app with managed identity
 description: Configure an Azure Managed Application with managed identity for linking to existing resources, managing Azure resources, and providing operational identity for Activity Log.
 ms.topic: conceptual
-ms.date: 07/19/2023
+ms.date: 06/24/2024
 ms.custom: subject-rbac-steps
 ---
 
 # Azure Managed Application with managed identity
 
 > [!NOTE]
-> Managed identity support for Azure Managed Applications is currently in preview. Please use the 2018-09-01-preview api version to utilize managed identity.
+> Managed identity support for Azure Managed Applications is currently in preview. Use the 2018-09-01-preview api version to utilize managed identity.
 
 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).
 
@@ -305,7 +305,7 @@ Once the managed application package is created, the managed application can be
 
 ## Accessing the managed identity token
 
-The token of the managed application can now be accessed through the `listTokens` api from the publisher tenant. An example request might look like:
+The token of the managed application can now be accessed through the `listTokens` API from the publisher tenant. An example request might look like:
 
 ```http
 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

@@ -2,7 +2,7 @@
 title: Azure managed applications with notifications
 description: Configure an Azure managed application with webhook endpoints to receive notifications about creates, updates, deletes, and errors on the managed application instances.
 ms.topic: how-to
-ms.date: 08/18/2022
+ms.date: 06/24/2024
 ---
 
 # Azure managed applications with notifications
@@ -69,27 +69,27 @@ For more information, see [Create an Azure application offer](../../marketplace/
 
 The following table describes all the possible combinations of `eventType` and `provisioningState` and their triggers:
 
-EventType | ProvisioningState | Trigger for notification
----|---|---
-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).
-PUT | Succeeded | Full provisioning of the managed application succeeded after a PUT.
-PUT | Failed | Failure of PUT of application instance provisioning at any point.
-PATCH | Succeeded | After a successful PATCH on the managed application instance to update tags, JIT access policy, or managed identity.
-DELETE | Deleting | As soon as the user initiates a DELETE of a managed app instance.
-DELETE | Deleted | After the full and successful deletion of the managed application.
-DELETE | Failed | After any error during the deprovisioning process that blocks the deletion.
+| EventType | ProvisioningState | Trigger for notification |
+| --- | --- | --- |
+| PUT | Accepted | Managed resource group was created and projected successfully after application PUT (before the deployment inside the managed resource group is kicked off). |
+| PUT | Succeeded | Full provisioning of the managed application succeeded after a PUT. |
+| PUT | Failed | Failure of PUT of application instance provisioning at any point. |
+| PATCH | Succeeded | After a successful PATCH on the managed application instance to update tags, just-in-time (JIT) access policy, or managed identity. |
+| DELETE | Deleting | As soon as the user initiates a DELETE of a managed app instance. |
+| DELETE | Deleted | After the full and successful deletion of the managed application. |
+| DELETE | Failed | After any error during the deprovisioning process that blocks the deletion. |
 
 ## Notification schema
 
-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.
+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.
 
 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`.
 
 ### Service catalog application notification schema
 
 The following sample shows a service catalog notification after the successful provisioning of a managed application instance.
 
-``` HTTP
+```HTTP
 POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_parameter_value} HTTP/1.1
 
 {
@@ -101,9 +101,9 @@ POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_paramet
 }
 ```
 
-If the provisioning fails, a notification with the error details will be sent to the specified endpoint.
+If provisioning fails, a notification with the error details is sent to the specified endpoint.
 
-``` HTTP
+```HTTP
 POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_parameter_value} HTTP/1.1
 
 {
@@ -129,7 +129,7 @@ POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_paramet
 
 The following sample shows a service catalog notification after the successful provisioning of a managed application instance.
 
-``` HTTP
+```HTTP
 POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_parameter_value} HTTP/1.1
 
 {
@@ -149,9 +149,9 @@ POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_paramet
 }
 ```
 
-If the provisioning fails, a notification with the error details will be sent to the specified endpoint.
+If provisioning fails, a notification with the error details is sent to the specified endpoint.
 
-``` HTTP
+```HTTP
 POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_parameter_value} HTTP/1.1
 
 {
@@ -181,16 +181,16 @@ POST https://{your_endpoint_URI}/resource?{optional_parameter}={optional_paramet
 }
 ```
 
-Property | Description
----|---
-`eventType` | The type of event that triggered the notification. (For example, PUT, PATCH, DELETE.)
-`applicationId` | The fully qualified resource identifier of the managed application for which the notification was triggered.
-`eventTime` | The timestamp of the event that triggered the notification. (Date and time in UTC ISO 8601 format.)
-`provisioningState` | The provisioning state of the managed application instance. For example, Succeeded, Failed, Deleting, Deleted.
-`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.
-`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.
-`plan` | _Specified only for Azure Marketplace managed applications_. Represents the publisher, offer, SKU, and version of the managed application instance.
-`error` | _Specified only when the provisioningState is Failed_. Contains the error code, message, and details of the issue that caused the failure.
+| Property | Description |
+| --- | --- |
+| `eventType` | The type of event that triggered the notification. For example, PUT, PATCH, DELETE. |
+| `applicationId` | The fully qualified resource identifier of the managed application for which the notification was triggered. |
+| `eventTime` | The timestamp of the event that triggered the notification. Date and time in UTC ISO 8601 format. |
+| `provisioningState` | The provisioning state of the managed application instance. For example, Succeeded, Failed, Deleting, Deleted. |
+| `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. |
+| `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. |
+| `plan` | _Specified only for Azure Marketplace managed applications_. Represents the publisher, offer, SKU, and version of the managed application instance. |
+| `error` | _Specified only when the provisioningState is Failed_. Contains the error code, message, and details of the issue that caused the failure. |
 
 ## Endpoint authentication
 
@@ -201,4 +201,4 @@ To secure the webhook endpoint and ensure the authenticity of the notification:
 
 ## Notification retries
 
-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.
+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

@@ -3,7 +3,7 @@ title: Create and publish Azure Managed Application in service catalog
 description: Describes how to create and publish an Azure Managed Application in your service catalog using Azure PowerShell, Azure CLI, or Azure portal.
 ms.topic: quickstart
 ms.custom: subject-armqs, devx-track-azurecli, devx-track-azurepowershell, subject-rbac-steps, mode-api, mode-arm, devx-track-arm-template, engagement-fy23
-ms.date: 05/29/2024
+ms.date: 06/24/2024
 ---
 
 # Quickstart: Create and publish an Azure Managed Application definition

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

@@ -3,7 +3,7 @@ title: Bring your own storage to create and publish an Azure Managed Application
 description: Describes how to bring your own storage to create and publish an Azure Managed Application definition in your service catalog.
 ms.topic: quickstart
 ms.custom: subject-armqs, devx-track-azurecli, devx-track-azurepowershell, subject-rbac-steps, mode-api, mode-arm, devx-track-arm-template, engagement-fy23
-ms.date: 05/29/2024
+ms.date: 06/24/2024
 ---
 
 # Quickstart: Bring your own storage to create and publish an Azure Managed Application definition