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

Author: asudbring

.openpublishing.redirection.azure-monitor.json

@@ -1,5 +1,15 @@
 {
     "redirections": [
+        {
+            "source_path_from_root": "/articles/azure-monitor/change/change-analysis-query.md",
+            "redirect_url": "/azure/azure-monitor/change/change-analysis-visualizations",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/change/change-analysis-custom-filters.md",
+            "redirect_url": "/azure/azure-monitor/change/change-analysis-visualizations",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/azure-monitor/change/change-analysis-powershell.md",
             "redirect_url": "/azure/azure-monitor/change/change-analysis",

articles/active-directory/governance/entitlement-management-access-package-approval-policy.md

@@ -155,7 +155,7 @@ For example, if you listed Alice and Bob as the first stage approver(s), list Ca
 
 1. In the **Forward to alternate approver(s) after how many days** box, put in the number of days the approvers have to approve or deny a request. If no approvers have approved or denied the request before the request duration, the request expires (timeout), and the user will have to submit another request for the access package. 
 
-    Requests can only be forwarded to alternate approvers a day after the request duration reaches half-life, and the decision of the main approver(s) has to time out after at least four days. If the request time-out is less or equal than three, there isn't enough time to forward the request to alternate approver(s). In this example, the duration of the request is 14 days. So, the request duration reaches half-life at day 7. So the request can't be forwarded earlier than day 8. Also, requests can't be forwarded on the last day of the request duration. So in the example, the latest the request can be forwarded is day 13.
+    Requests can only be forwarded to alternate approvers a day after the request has been initiated. To use alternate approval, the request time-out needs to be at least 4 days.
 
 ## Enable requests
 

articles/active-directory/governance/media/entitlement-management-access-package-approval-policy/alternate-approvers-add.png

@@ -1,21 +1,21 @@
 ---
-title: Visualizations for Change Analysis in Azure Monitor
-description: Learn how to use visualizations in Azure Monitor's Change Analysis.
+title: Scenarios for using Change Analysis in Azure Monitor
+description: Learn the various scenarios in which you can use Azure Monitor's Change Analysis.
 ms.topic: conceptual
 ms.author: hannahhunter
 author: hhunter-ms
 ms.contributor: cawa
-ms.date: 07/28/2022
+ms.date: 01/12/2023
 ms.subservice: change-analysis
 ms.custom: devx-track-azurepowershell
 ms.reviewer: cawa
 ---
 
-# Visualizations for Change Analysis in Azure Monitor
+# Scenarios for using Change Analysis in Azure Monitor
 
-Change Analysis provides data for various management and troubleshooting scenarios to help you understand what changes to your application might have caused the issues. You can view the Change Analysis data through several channels: 
+Change Analysis provides data for various management and troubleshooting scenarios to help you understand what changes to your application might have caused the issues. 
 
-## Change Analysis overview portal
+## View Change Analysis data
 
 You can access the Change Analysis overview portal under Azure Monitor, where you can view all changes and application dependency/resource insights. You can access Change Analysis through a couple of entry points:
 
@@ -138,6 +138,90 @@ You can also drill to Change Analysis logs via a chart you've created or pinned
 
    :::image type="content" source="./media/change-analysis/view-change-analysis-2.png" alt-text="Drill into logs and select to view Change Analysis.":::
 
+## Browse using custom filters and search bar
+
+Browsing through a long list of changes in the entire subscription is time consuming. With Change Analysis custom filters and search capability, you can efficiently navigate to changes relevant to issues for troubleshooting.
+
+:::image type="content" source="./media/change-analysis/filters-search-bar.png" alt-text="Screenshot showing that filters and search bar are available at the top of Change Analysis homepage, right above the changes section.":::
+
+### Filters
+
+| Filter | Description |
+| ------ | ----------- |
+| Subscription | This filter is in-sync with the Azure portal subscription selector. It supports multiple-subscription selection. |
+| Time range | Specifies how far back the UI display changes, up to 14 days. By default, it’s set to the past 24 hours. |
+| Resource group | Select the resource group to scope the changes. By default, all resource groups are selected. |
+| Change level | Controls which levels of changes to display. Levels include: important, normal, and noisy. </br> **Important:** related to availability and security </br> **Noisy:** Read-only properties that are unlikely to cause any issues </br> By default, important and normal levels are checked. |
+| Resource | Select **Add filter** to use this filter. </br> Filter the changes to specific resources. Helpful if you already know which resources to look at for changes. [If the filter is only returning 1,000 resources, see the corresponding solution in troubleshooting guide](./change-analysis-troubleshoot.md#cant-filter-to-your-resource-to-view-changes). |
+| Resource type | Select **Add filter** to use this filter. </br> Filter the changes to specific resource types. |
+
+### Search bar
+
+The search bar filters the changes according to the input keywords. Search bar results apply only to the changes loaded by the page already and don't pull in results from the server side.
+
+## Pin and share a Change Analysis query to the Azure dashboard
+
+Let's say you want to curate a change view on specific resources, like all Virtual Machine changes in your subscription, and include it in a report sent periodically. You can pin the view to an Azure dashboard for monitoring or sharing scenarios. If you'd like to share a specific change with your team members, you can use the share feature in the Change Details page.
+
+## Pin to the Azure dashboard
+
+Once you have applied filters to the Change Analysis homepage:
+
+1. Select **Pin current filters** from the top menu. 
+1. Enter a name for the pin. 
+1. Click **OK** to proceed.
+
+   :::image type="content" source="./media/change-analysis/click-pin-menu.png" alt-text="Screenshot of selecting Pin current filters button in Change Analysis.":::
+
+A side pane will open to configure the dashboard where you'll place your pin. You can select one of two dashboard types:
+
+| Dashboard type | Description |
+| -------------- | ----------- |
+| Private | Only you can access a private dashboard. Choose this option if you're creating the pin for your own easy access to the changes. |
+| Shared | A shared dashboard supports role-based access control for view/read access. Shared dashboards are created as a resource in your subscription with a region and resource group to host it. Choose this option if you're creating the pin to share with your team. |
+
+### Select an existing dashboard
+
+If you already have a dashboard to place the pin:
+
+1. Select the **Existing** tab.
+1. Select either **Private** or **Shared**.
+1. Select the dashboard you'd like to use. 
+1. If you've selected **Shared**, select the subscription in which you'd like to place the dashboard.
+1. Select **Pin**.
+ 
+   :::image type="content" source="./media/change-analysis/existing-dashboard-small.png" alt-text="Screenshot of selecting an existing dashboard to pin your changes to. ":::
+
+### Create a new dashboard
+
+You can create a new dashboard for this pin.
+ 
+1. Select the **Create new** tab. 
+1. Select either **Private** or **Shared**. 
+1. Enter the name of the new dashboard.
+1. If you're creating a shared dashboard, enter the resource group and region information. 
+1. Click **Create and pin**. 
+
+   :::image type="content" source="./media/change-analysis/create-pin-dashboard-small.png" alt-text="Screenshot of creating a new dashboard to pin your changes to.":::
+
+Once the dashboard and pin are created, navigate to the Azure dashboard to view them.
+
+1. From the Azure portal home menu, select **Dashboard**. Use the **Manage Sharing** button in the top menu to handle access or "unshare". Click on the pin to navigate to the curated view of changes.
+
+   :::image type="content" source="./media/change-analysis/azure-dashboard.png" alt-text="Screenshot of selecting the Dashboard in the Azure portal home menu.":::
+
+   :::image type="content" source="./media/change-analysis/view-share-dashboard.png" alt-text="Screenshot of the pin in the dashboard.":::
+
+## Share a single change with your team
+
+In the Change Analysis homepage, select a line of change to view details on the change.
+
+1. On the Changed properties page, select **Share** from the top menu. 
+1. On the Share Change Details pane, copy the deep link of the page and share with your team in messages, emails, reports, or whichever communication channel your team prefers.
+
+   :::image type="content" source="./media/change-analysis/share-single-change.png" alt-text="Screenshot of selecting the share button on the dashboard and copying link.":::
+
+
 ## Next steps
 
 - Learn how to [troubleshoot problems in Change Analysis](change-analysis-troubleshoot.md)

articles/azure-monitor/change/change-analysis-custom-filters.md

@@ -64,7 +64,7 @@ Read more about distributed tracing at [What is distributed tracing?](app/distri
 
 Once [Change Analysis is enabled](./change/change-analysis-enable.md), the `Microsoft.ChangeAnalysis` resource provider is registered with an Azure Resource Manager subscription to make the resource properties and configuration change data available. Change Analysis provides data for various management and troubleshooting scenarios to help users understand what changes might have caused the issues:
 - Troubleshoot your application via the [Diagnose & solve problems tool](./change/change-analysis-enable.md).
-- Perform general management and monitoring via the [Change Analysis overview portal](./change/change-analysis-visualizations.md#change-analysis-overview-portal) and [the activity log](./change/change-analysis-visualizations.md#activity-log-change-history).
+- Perform general management and monitoring via the [Change Analysis overview portal](./change/change-analysis-visualizations.md#view-change-analysis-data) and [the activity log](./change/change-analysis-visualizations.md#activity-log-change-history).
 - [Learn more about how to view data results for other scenarios](./change/change-analysis-visualizations.md).
 
 Read more about Change Analysis, including data sources in [Use Change Analysis in Azure Monitor](./change/change-analysis.md).

articles/azure-monitor/change/change-analysis-query.md

@@ -1303,10 +1303,6 @@ items:
       href: change/change-analysis-enable.md
     - name: Visualizations
       href: change/change-analysis-visualizations.md
-    - name: Custom filters
-      href: change/change-analysis-custom-filters.md
-    - name: Pin and share changes via Azure dashboard
-      href: change/change-analysis-query.md
     - name: Troubleshoot
       href: change/change-analysis-troubleshoot.md
 - name: Respond

articles/azure-monitor/change/change-analysis-visualizations.md

@@ -18,7 +18,7 @@
 - name: Samples
   items:
   - name: Azure CLI
-    items: 
+    items:
     - name: Overview
       href: cli-samples.md
     - name: Create managed application
@@ -81,7 +81,7 @@
       href: reference-view-definition-artifact.md
   - name: Azure CLI
     href: /cli/azure/managedapp
-  - name: PowerShell
+  - name: Azure PowerShell
     href: /powershell/module/az.resources/
   - name: REST
     href: /rest/api/managedapplications/