Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr

Author: inward-eye

articles/azure-monitor/agents/azure-monitor-agent-extension-versions.md

@@ -4,7 +4,7 @@ description: This article describes the version details for the Azure Monitor ag
 ms.topic: conceptual
 author: shseth
 ms.author: shseth
-ms.date: 7/21/2022
+ms.date: 8/22/2022
 ms.custom: references_region
 ms.reviewer: shseth
 
@@ -19,7 +19,8 @@ We strongly recommended to update to the latest version at all times, or opt in
 ## Version details
 | Release Date | Release notes | Windows | Linux |  
 |:---|:---|:---|:---| 
-| June 2022 | Bugfixes with user assigned identity support, and reliability improvements | 1.6.0.0 | Coming soon | 
+| July 2022 | Fix for mismatch event timestamps for Sentinel Windows Event Forwarding | 1.7.0.0 | None | 
+| June 2022 | Bugfixes with user assigned identity support, and reliability improvements | 1.6.0.0 | None | 
 | May 2022 | <ul><li>Fixed issue where agent stops functioning due to faulty XPath query. With this version, only query related Windows events will fail, other data types will continue to be collected</li><li>Collection of Windows network troubleshooting logs added to 'CollectAMAlogs.ps1' tool</li><li>Linux support for Debian 11 distro</li><li>Fixed issue to list mount paths instead of device names for Linux disk metrics</li></ul> | 1.5.0.0 | 1.21.0 |
 | April 2022 | <ul><li>Private IP information added in Log Analytics <i>Heartbeat</i> table for Windows and Linux</li><li>Fixed bugs in Windows IIS log collection (preview) <ul><li>Updated IIS site column name to match backend KQL transform</li><li>Added delay to IIS upload task to account for IIS buffering</li></ul></li><li>Fixed Linux CEF syslog forwarding for Sentinel</li><li>Removed 'error' message for Azure MSI token retrieval failure on Arc to show as 'Info' instead</li><li>Support added for Ubuntu 22.04, RHEL 8.5, 8.6, AlmaLinux and RockyLinux distros</li></ul> | 1.4.1.0<sup>Hotfix</sup> | 1.19.3 |
 | March 2022 | <ul><li>Fixed timestamp and XML format bugs in Windows Event logs</li><li>Full Windows OS information in Log Analytics Heartbeat table</li><li>Fixed Linux performance counters to collect instance values instead of 'total' only</li></ul> | 1.3.0.0 | 1.17.5.0 |

articles/azure-resource-manager/managed-applications/media/overview/access.png

@@ -1,38 +1,38 @@
 ---
 title: Overview of Azure Managed Applications
-description: Describes the concepts for Azure Managed Applications that provide cloud solutions that are easy for consumers to deploy and operate.
+description: Describes the concepts for Azure Managed Applications that provide cloud solutions that are easy for customers to deploy and operate.
 author: davidsmatlak
 ms.author: davidsmatlak
 ms.topic: overview
-ms.date: 08/03/2022
+ms.date: 08/19/2022
 ---
 
 # Azure Managed Applications overview
 
-Azure Managed Applications enable you to offer cloud solutions that are easy for consumers to deploy and operate. You implement the infrastructure and provide ongoing support. To make a managed application available to all customers, publish it in Azure Marketplace. To make it available to only users in your organization, publish it to an internal catalog.
+Azure Managed Applications enable you to offer cloud solutions that are easy for customers to deploy and operate. You implement the infrastructure and provide ongoing support. To make a managed application available to all customers, publish it in Azure Marketplace. To make it available to only users in your organization, publish it to an internal catalog.
 
-A managed application is similar to a solution template in Azure Marketplace, with one key difference. In a managed application, the resources are deployed to a resource group that's managed by the publisher of the app. The resource group is present in the consumer's subscription, but an identity in the publisher's tenant has access to the resource group. As the publisher, you specify the cost for ongoing support of the solution.
+A managed application is similar to a solution template in Azure Marketplace, with one key difference. In a managed application, the resources are deployed to a resource group that's managed by the publisher of the app. The resource group is present in the customer's subscription, but an identity in the publisher's tenant has access to the resource group. As the publisher, you specify the cost for ongoing support of the solution.
 
 > [!NOTE]
 > The documentation for Azure Custom Providers used to be included with Managed Applications. That documentation was moved to [Azure Custom Providers](../custom-providers/overview.md).
 
 ## Advantages of managed applications
 
-Managed applications reduce barriers to consumers using your solutions. They don't need expertise in cloud infrastructure to use your solution. Consumers have limited access to the critical resources and don't need to worry about making a mistake when managing it.
+Managed applications reduce barriers to customers using your solutions. They don't need expertise in cloud infrastructure to use your solution. Customers have limited access to the critical resources and don't need to worry about making a mistake when managing it.
 
-Managed applications enable you to establish an ongoing relationship with your consumers. You define terms for managing the application and all charges are handled through Azure billing.
+Managed applications enable you to establish an ongoing relationship with your customers. You define terms for managing the application and all charges are handled through Azure billing.
 
 Although customers deploy managed applications in their subscriptions, they don't have to maintain, update, or service them. You can make sure that all customers are using approved versions. Customers don't have to develop application-specific domain knowledge to manage these applications. Customers automatically acquire application updates without the need to worry about troubleshooting and diagnosing issues with the applications.
 
 For IT teams, managed applications enable you to offer pre-approved solutions to users in the organization. You know these solutions are compliant with organizational standards.
 
-Managed Applications support [managed identities for Azure resources](./publish-managed-identity.md).
+Managed applications support [managed identities for Azure resources](./publish-managed-identity.md).
 
 ## Types of managed applications
 
 You can publish your managed application either internally in the service catalog or externally in Azure Marketplace.
 
-:::image type="content" source="./media/overview/manage_app_options.png" alt-text="Diagram that shows how a managed application is published to service catalog or Azure Marketplace.":::
+:::image type="content" source="./media/overview/managed-apps-options.png" alt-text="Diagram that shows how a managed application is published to service catalog or Azure Marketplace.":::
 
 ### Service catalog
 
@@ -48,27 +48,35 @@ For information about publishing a managed application to Azure Marketplace, see
 
 ## Resource groups for managed applications
 
-Typically, the resources for a managed application are in two resource groups. The consumer manages one resource group, and the publisher manages the other resource group. When the managed application is defined, the publisher specifies the levels of access. The publisher can request either a permanent role assignment, or [just-in-time access](request-just-in-time-access.md) for an assignment that is constrained to a time period.
+Typically, the resources for a managed application are in two resource groups. The customer manages one resource group, and the publisher manages the other resource group. When the managed application is defined, the publisher specifies the levels of access. The publisher can request either a permanent role assignment, or [just-in-time access](request-just-in-time-access.md) for an assignment that's constrained to a time period.
 
 Restricting access for [data operations](../../role-based-access-control/role-definitions.md) is currently not supported for all data providers in Azure.
 
-The following image shows a scenario where the publisher requests the owner role for the managed resource group. The publisher placed a read-only lock on this resource group for the consumer. The publisher's identities that are granted access to the managed resource group are exempt from the lock.
+The following image shows the relationship between the customer's Azure subscription and the publisher's Azure subscription. The managed application and managed resource group are in the customer's subscription. The publisher has management access to the managed resource group to maintain the managed application's resources. The publisher places a read-only lock on the managed resource group that limits the customer's access to manage resources. The publisher's identities that have access to the managed resource group are exempt from the lock.
 
-:::image type="content" source="./media/overview/access.png" alt-text="Diagram that shows access to a managed resource group and application resource group.":::
+:::image type="content" source="./media/overview/managed-apps-resource-group.png" alt-text="Diagram that shows the relationship between customer and publisher Azure subscriptions for a managed resource group.":::
 
 ### 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](/azure/templates/microsoft.solutions/applications).
+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).
 
-The consumer has full access to the resource group and uses it to manage the lifecycle of the managed application.
+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, this resource group contains the virtual machines, storage accounts, and virtual networks for the solution. The consumer has limited access to this resource group because the consumer 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.
+This resource group holds all the resources that are required by the managed application. For example, this resource group contains the virtual machines, storage accounts, and virtual networks for the solution. The customer has limited access to this resource group because 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.
 
-When the [managed application is published to the marketplace](../../marketplace/azure-app-offer-setup.md), the publisher can grant consumers the ability to perform specific actions on resources in the managed resource group. For example, the publisher can specify that consumers can restart virtual machines. All other actions beyond read actions are still denied. Changes to resources in a managed resource group by a consumer with granted actions are subject to the [Azure Policy](../../governance/policy/overview.md) assignments within the consumer's tenant scoped to include 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. 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.
 
-When the consumer deletes the managed application, the managed resource group is also deleted.
+When the customer deletes the managed application, the managed resource group is also deleted.
+
+## Resource provider
+
+Managed applications use the `Microsoft.Solutions` resource provider with ARM template JSON. For more information, see the resource types and API versions.
+
+- [Microsoft.Solutions/applicationDefinitions](/azure/templates/microsoft.solutions/applicationdefinitions?pivots=deployment-language-arm-template)
+- [Microsoft.Solutions/applications](/azure/templates/microsoft.solutions/applications?pivots=deployment-language-arm-template)
+- [Microsoft.Solutions/jitRequests](/azure/templates/microsoft.solutions/jitrequests?pivots=deployment-language-arm-template)
 
 ## Azure Policy
 
@@ -79,4 +87,4 @@ You can apply an [Azure Policy](../../governance/policy/overview.md) to audit yo
 In this article, you learned about benefits of using managed applications. Go to the next article to create a managed application definition.
 
 > [!div class="nextstepaction"]
-> [Quickstart: Create and publish a managed application definition](publish-service-catalog-app.md)
+> [Quickstart: Create and publish an Azure managed application definition](publish-service-catalog-app.md)

…ns/media/overview/manage_app_options.png …/media/overview/managed-apps-options.pngarticles/azure-resource-manager/managed-applications/media/overview/manage_app_options.png renamed to articles/azure-resource-manager/managed-applications/media/overview/managed-apps-options.png articles/azure-resource-manager/managed-applications/media/overview/manage_app_options.png renamed to articles/azure-resource-manager/managed-applications/media/overview/managed-apps-options.png

@@ -6,7 +6,7 @@ ms.author: nayenama
 ms.service: purview
 ms.subservice: purview-workflows
 ms.topic: how-to #Required; leave this attribute/value as-is.
-ms.date: 03/09/2022
+ms.date: 08/22/2022
 ms.custom: template-how-to #Required; leave this attribute/value as-is.
 ---
 
@@ -68,17 +68,17 @@ Select the request to take action.
 
 1. Select the correct status, add any comments, and select **Confirm**.
 
-### Re-assign requests
+### Reassign requests
 
-You can re-assign requests both approvals and tasks which are assigned to you to a different user.
+You can reassign requests both approvals and tasks that are assigned to you to a different user.
 
-1. To re-assign, select request or task you are assigned and click on **Reassign** in the following window.
+1. To reassign, select the request or task you're assigned and select **Reassign** in the following window.
 
-    :::image type="content" source="./media/how-to-workflow-manage-requests-approval/reassign-button.png" alt-text="Screenshot showing the task selected and the Respond page is open, with details, a status, and a place for comments and re-assign button.":::
+    :::image type="content" source="./media/how-to-workflow-manage-requests-approval/reassign-button.png" alt-text="Screenshot showing the task selected and the Respond page is open, with details, a status, and a place for comments and reassign button.":::
 
-1. You will be not presented with a list of all the users who are assigned to the request. Click on **Assignee**  where your user name or the group you are part of will be displayed and change it from your user name to the new user name. Click **Save** to complete the re-assignment. 
+1. You'll be presented with a list of all the users who are assigned to the request. Select **Assignee**  where your user name or the group you're part of is displayed and change it from your user name to the new user name. Select **Save** to complete the reassignment. 
 
-    :::image type="content" source="./media/how-to-workflow-manage-requests-approval/reassign-user.png" alt-text="Screenshot showing the request selected and the re-assign user.":::
+    :::image type="content" source="./media/how-to-workflow-manage-requests-approval/reassign-user.png" alt-text="Screenshot showing the request selected and the reassign user.":::
 
     > [!NOTE]
     > You can only re-assign your user id or group you are part of to another user or group. The other assignees will be greyed out and will not available for re-assignment.
@@ -93,12 +93,12 @@ Select the request to see the status and the outcomes for each approver/task own
 
 ### Cancel workflows
 
-You can cancel a submitted request and it's underlying workflow by clicking on **Cancel request and it's underlying workflow run**.
+You can cancel a submitted request and its underlying workflow by selecting **Cancel request and its underlying workflow run**.
 
 :::image type="content" source="./media/how-to-workflow-manage-requests-approval/cancel-workflow-request.png" alt-text="Screenshot with the requests and approvals page shown on the 'My pending requests' tab, with cancel request.":::
 
    > [!NOTE]
-   > You can only cancel workflows which are in progress. When you cancel a request from requests and approvals section, it will cancel underlying workflow run.
+   > You can only cancel workflows that are in progress. When you cancel a request from the **requests and approvals** section, it will cancel the underlying workflow run.
 
 
 ## History

articles/azure-resource-manager/managed-applications/media/overview/managed-apps-resource-group.png

@@ -38,12 +38,12 @@ This article outlines how to manage workflows that are already running.
 
     :::image type="content" source="./media/how-to-workflow-manage-runs/select-stages.png" alt-text="Screenshot of the workflow runs page, with the workflow details page overlaid. Some workflow run actions in the request timeline have been expanded to show more information and sub steps.":::
 
-1. You can cancel a running workflow by clicking on **Cancel workflow run**.
+1. You can cancel a running workflow by selecting **Cancel workflow run**.
 
-    :::image type="content" source="./media/how-to-workflow-manage-runs/cancel-workflows.png" alt-text="Screenshot of the workflow runs page, with the workflow details page overlaid and cancel button to cancel the workflow run.":::
+    :::image type="content" source="./media/how-to-workflow-manage-runs/cancel-workflows-inline.png" alt-text="Screenshot of the workflow runs page, with the workflow details page overlaid and cancel button to cancel the workflow run." lightbox="./media/how-to-workflow-manage-runs/cancel-workflows.png":::
 
     > [!NOTE]
-    > You can only cancel workflows which are in progress.
+    > You can only cancel workflows that are in progress.
 
 
 ## Next steps