Merge pull request #279098 from davidsmatlak/ds-updates-ama-20240624-3

Freshness updates for Managed Apps content

Author: JamesJBarnett

articles/azure-resource-manager/managed-applications/existing-vnet-integration.md

@@ -2,7 +2,7 @@
 title: Deploy to existing virtual network
 description: Describes how to enable users of your managed application to select an existing virtual network. The virtual network can be outside of the managed application.
 ms.topic: how-to
-ms.date: 05/11/2020
+ms.date: 06/24/2024
 ---
 
 # Use existing virtual network with Azure Managed Applications
@@ -11,7 +11,7 @@ This article shows you how to define an Azure Managed Application that integrate
 
 ## Main template
 
-First, let's look at the _mainTemplate.json_ file. The whole template for deploying a virtual machine and its associated resources is shown below. Later, you'll examine more closely the parts of the template that are related to using an existing virtual network.
+First, let's look at the _mainTemplate.json_ file. The whole template for deploying a virtual machine and its associated resources is shown. Later, you review the parts of the template that are related to using an existing virtual network.
 
 :::code language="json" source="~/resourcemanager-templates/managed-app-existing-vnet/mainTemplate.json":::
 
@@ -46,7 +46,7 @@ That element lets the consumer select either a new or existing virtual network.
 In the outputs, you include a value that indicates whether the consumer selected a new or existing virtual network. There's also a managed identity value.
 
 > [!NOTE]
-> The output value for the managed identity must be named **managedIdentity**.
+> The output value for the managed identity must be named `managedIdentity`.
 
 :::code language="json" source="~/resourcemanager-templates/managed-app-existing-vnet/createUiDefinition.json" range="136-148" highlight="6,12":::
 

articles/azure-resource-manager/managed-applications/monitor-managed-application-portal.md

@@ -2,12 +2,12 @@
 title: Use Azure portal to monitor a managed app
 description: Shows how to use the Azure portal to monitor availability and alerts for a managed application.
 ms.topic: how-to
-ms.date: 10/04/2018
+ms.date: 06/24/2024
 ---
 
 # Monitor a deployed instance of a managed application
 
-After you've deployed a managed application to your Azure subscription, you may want to check the status of the application. This article shows options in the Azure portal for checking the status. You can monitor the availability of the resources in your managed application. You can also set up and view alerts.
+After you deploy a managed application to your Azure subscription, you might want to check the status of the application. This article shows options in the Azure portal for checking the status. You can monitor the availability of the resources in your managed application. You can also set up and view alerts.
 
 ## View resource health
 
@@ -29,7 +29,7 @@ After you've deployed a managed application to your Azure subscription, you may
 
    ![Select alerts](./media/monitor-managed-application-portal/select-alerts.png)
 
-1. If you have alert rules configured, you see information about alerts that have been raised.
+1. If you have alert rules configured, you see information about alerts that were raised.
 
    ![View alerts](./media/monitor-managed-application-portal/view-alerts.png)
 
@@ -41,5 +41,5 @@ You can create alerts for your managed application instance or the resources in
 
 ## Next steps
 
-* For managed application examples, see [Sample projects for Azure managed applications](sample-projects.md).
-* To deploy a managed application, see [Deploy service catalog app through Azure portal](deploy-service-catalog-quickstart.md).
+- For managed application examples, see [Sample projects for Azure managed applications](sample-projects.md).
+- To deploy a managed application, see [Deploy service catalog app through Azure portal](deploy-service-catalog-quickstart.md).

articles/azure-resource-manager/managed-applications/overview.md

@@ -2,7 +2,7 @@
 title: Overview of Azure Managed Applications
 description: Describes the concepts for Azure Managed Applications that provide cloud solutions that are easy for customers to deploy and operate.
 ms.topic: overview
-ms.date: 07/31/2023
+ms.date: 06/24/2024
 ---
 
 # Azure Managed Applications overview
@@ -73,13 +73,13 @@ The management access as shown in the image can be changed. The customer can be
 
 ### Application resource group
 
-This resource group holds the managed application instance. This resource group may only contain one resource. The resource type of the managed application is [Microsoft.Solutions/applications](#resource-provider).
+This resource group holds the managed application instance. This resource group might only contain one resource. The resource type of the managed application is [Microsoft.Solutions/applications](#resource-provider).
 
 The customer has full access to the resource group and uses it to manage the lifecycle of the managed application.
 
 ### Managed resource group
 
-This resource group holds all the resources that are required by the managed application. For example, an application's virtual machines, storage accounts, and virtual networks. The customer might have limited access to this resource group because unless permission options are changed, the customer doesn't manage the individual resources for the managed application. The publisher's access to this resource group corresponds to the role specified in the managed application definition. For example, the publisher might request the Owner or Contributor role for this resource group. The access is either permanent or limited to a specific time. The publisher can choose to not have access to the managed resource group.
+This resource group holds all the resources required by the managed application. For example, an application's virtual machines, storage accounts, and virtual networks. The customer might have limited access to this resource group because unless permission options are changed, the customer doesn't manage the individual resources for the managed application. The publisher's access to this resource group corresponds to the role specified in the managed application definition. For example, the publisher might request the Owner or Contributor role for this resource group. The access is either permanent or limited to a specific time. The publisher can choose to not have access to the managed resource group.
 
 When the [managed application is published to the marketplace](../../marketplace/azure-app-offer-setup.md), the publisher can grant customers the ability to perform specific actions on resources in the managed resource group or be given full access. For example, the publisher can specify that customers can restart virtual machines. All other actions beyond read actions are still denied. Changes to resources in a managed resource group by a customer with granted actions are subject to the [Azure Policy](../../governance/policy/overview.md) assignments within the customer's tenant scoped to include the managed resource group.
 

articles/azure-resource-manager/managed-applications/policy-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Built-in policy definitions for Azure Managed Applications
 description: Lists Azure Policy built-in policy definitions for Azure Managed Applications. These built-in policy definitions provide common approaches to managing your Azure resources.
-ms.date: 02/06/2024
+ms.date: 06/24/2024
 ms.topic: reference
 ms.custom: subject-policy-reference
 ---

articles/azure-resource-manager/managed-applications/reference-createuidefinition-artifact.md

@@ -2,12 +2,12 @@
 title: CreateUiDefinition artifact
 description: Shows how to create the createUiDefinition artifact for an Azure Managed Application. The file is named createUiDefinition.json.
 ms.topic: reference
-ms.date: 07/11/2019
+ms.date: 06/24/2024
 ---
 
 # Reference: User interface elements artifact
 
-This article is a reference for a *createUiDefinition.json* artifact in Azure Managed Applications. For more information about authoring user interface elements, see [Create user interface elements](create-uidefinition-elements.md).
+This article is a reference for a _createUiDefinition.json_ artifact in Azure Managed Applications. For more information about authoring user interface elements, see [Create user interface elements](create-uidefinition-elements.md).
 
 ## User interface elements
 

articles/azure-resource-manager/managed-applications/request-just-in-time-access.md

@@ -3,12 +3,14 @@ title: Request just-in-time access
 description: Describes how publishers of Azure Managed Applications request just-in-time access to a managed application.
 author: MSEvanhi
 ms.topic: conceptual
-ms.date: 09/25/2020
+ms.date: 06/24/2024
 ms.author: evanhi
 ---
+
 # Enable and request just-in-time access for Azure Managed Applications
 
-Consumers of your managed application may be reluctant to grant you permanent access to the managed resource group. As a publisher of a managed application, you might prefer that consumers know exactly when you need to access the managed resources. To give consumers greater control over granting access to managed resources, Azure Managed Applications provides a feature called just-in-time (JIT) access.
+Consumers of your managed application might be reluctant to grant you permanent access to the managed resource group. As a publisher of a managed application, you might prefer that consumers know exactly when you need to access the managed resources. To give consumers greater control over granting access to managed resources, Azure Managed Applications provides a feature called just-in-time (JIT) access.
+
 JIT access enables you to request elevated access to a managed application's resources for troubleshooting or maintenance. You always have read-only access to the resources, but for a specific time period you can have greater access.
 
 The work flow for granting access is:
@@ -33,20 +35,20 @@ In "steps":
 
 ```json
 {
-    "name": "jitConfiguration",
-    "label": "JIT Configuration",
-    "subLabel": {
-        "preValidation": "Configure JIT settings for your application",
-        "postValidation": "Done"
-    },
-    "bladeTitle": "JIT Configuration",
-    "elements": [
-        {
-          "name": "jitConfigurationControl",
-          "type": "Microsoft.Solutions.JitConfigurator",
-          "label": "JIT Configuration"
-        }
-    ]
+  "name": "jitConfiguration",
+  "label": "JIT Configuration",
+  "subLabel": {
+    "preValidation": "Configure JIT settings for your application",
+    "postValidation": "Done"
+  },
+  "bladeTitle": "JIT Configuration",
+  "elements": [
+    {
+      "name": "jitConfigurationControl",
+      "type": "Microsoft.Solutions.JitConfigurator",
+      "label": "JIT Configuration"
+    }
+  ]
 }
 ```
 
@@ -68,7 +70,7 @@ When creating your offer in Partner Center, make sure you enable JIT access.
 
    :::image type="content" source="./media/request-just-in-time-access/enable-just-in-time-access.png" alt-text="Enable just-in-time access":::
 
-You've added a JIT configuration step to your UI, and have enabled JIT access in the commercial marketplace offering. When consumers deploy your managed application, they can [turn on JIT access for their instance](approve-just-in-time-access.md#enable-during-deployment).
+You added a JIT configuration step to your UI, and enabled JIT access in the commercial marketplace offering. When consumers deploy your managed application, they can [turn on JIT access for their instance](approve-just-in-time-access.md#enable-during-deployment).
 
 ## Request access
 

articles/azure-resource-manager/managed-applications/sample-projects.md

@@ -2,7 +2,7 @@
 title: Sample projects
 description: Provides a summary of sample projects that are available for Azure Managed Applications.
 ms.topic: sample
-ms.date: 09/04/2019
+ms.date: 06/24/2024
 ---
 
 # Sample projects for Azure managed applications

articles/azure-resource-manager/managed-applications/test-createuidefinition.md

@@ -2,18 +2,18 @@
 title: Test the UI definition file
 description: Describes how to test the user experience for creating your Azure Managed Application through the portal.
 ms.topic: how-to
-ms.date: 06/04/2021
+ms.date: 06/24/2024
 ---
 
 # Test your portal interface for Azure Managed Applications
 
-After [creating the createUiDefinition.json file](create-uidefinition-overview.md) for your managed application, you need to test the user experience. To simplify testing, use a sandbox environment that loads your file in the portal. You don't need to actually deploy your managed application. The sandbox presents your user interface in the current, full-screen portal experience. The sandbox is the recommended way to preview the interface.
+After [creating the createUiDefinition.json file](create-uidefinition-overview.md) for your managed application, you need to test the user experience. To simplify testing, use a sandbox environment that loads your file in the portal. You don't need to actually deploy your managed application. The sandbox presents your user interface in the current full-screen portal experience. The sandbox is the recommended way to preview the interface.
 
 ## Prerequisites
 
-* A _createUiDefinition.json_ file. If you don't have this file, copy the [sample file](https://github.com/Azure/azure-quickstart-templates/blob/master/demos/100-marketplace-sample/createUiDefinition.json).
+- A _createUiDefinition.json_ file. If you don't have this file, copy the [sample file](https://github.com/Azure/azure-quickstart-templates/blob/master/demos/100-marketplace-sample/createUiDefinition.json).
 
-* An Azure subscription. If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.
+- An Azure subscription. If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.
 
 ## Use sandbox
 
@@ -31,7 +31,7 @@ After [creating the createUiDefinition.json file](create-uidefinition-overview.m
 
 ### Troubleshooting
 
-If your form doesn't display after selecting **Preview**, you may have a syntax error. Look for the red indicator on the right scroll bar and navigate to it.
+If your form doesn't display after selecting **Preview**, you might have a syntax error. Look for the red indicator on the right scroll bar and navigate to it.
 
 ![Show syntax error](./media/test-createuidefinition/show-syntax-error.png)
 
@@ -41,8 +41,8 @@ If your form doesn't display, and instead you see an icon of a cloud with tear d
 
 ## Test your solution files
 
-Now that you've verified your portal interface is working as expected, it's time to validate that your createUiDefinition file is properly integrated with your mainTemplate.json file. You can run a validation script test to test the content of your solution files, including the createUiDefinition file. The script validates the JSON syntax, checks for regex expressions on text fields, and makes sure the output values of the portal interface match the parameters of your template. For information on running this script, see [Run static validation checks for templates](https://aka.ms/arm-ttk).
+Now that you verified your portal interface is working as expected, it's time to validate that your createUiDefinition file is properly integrated with your mainTemplate.json file. You can run a validation script test to test the content of your solution files, including the createUiDefinition file. The script validates the JSON syntax, checks for regex expressions on text fields, and makes sure the output values of the portal interface match the parameters of your template. For information on running this script, see [Run static validation checks for templates](https://aka.ms/arm-ttk).
 
 ## Next steps
 
-After validating your portal interface, learn about making your [Azure managed application available in the Marketplace](../../marketplace/azure-app-offer-setup.md).
+After validating your portal interface, learn about making your [Azure Managed Application available in the Marketplace](/partner-center/marketplace-offers/azure-app-offer-setup).