Syncing with main. Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into work-faq-models

Author: Heidilohr

.openpublishing.publish.config.json

@@ -994,6 +994,7 @@
   ".openpublishing.redirection.app-service.json",
   ".openpublishing.redirection.azure-arc-data.json",
   ".openpublishing.redirection.azure-attestation.json",
+  ".openpublishing.redirection.azure-app-configuration.json",
   ".openpublishing.redirection.azure-australia.json",
   ".openpublishing.redirection.azure-databricks.json",
   ".openpublishing.redirection.azure-hpc.json",

.openpublishing.redirection.azure-app-configuration.json

@@ -0,0 +1,9 @@
+{
+  "redirections": [
+    {
+      "source_path_from_root": "/articles/azure-app-configuration/howto-backup-config-store.md",
+      "redirect_url": "/articles/azure-app-configuration/concept-geo-replication.md",
+      "redirect_document_id": false
+    }
+  ]
+}

.openpublishing.redirection.healthcare-apis.json

@@ -550,33 +550,61 @@
           "redirect_document_id": false
       },
       {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-iot-connector-in-azure.md",
-          "redirect_url": "/azure/healthcare-apis/iot/deploy-new-choose",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
           "redirect_document_id": false
       },
       {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-02-new-button.md",
-          "redirect_url": "/azure/healthcare-apis/iot/deploy-new-button",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
           "redirect_document_id": false
       },
       {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-03-new-manual.md",
-          "redirect_url": "/azure/healthcare-apis/iot/deploy-new-manual",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
           "redirect_document_id": false
       },
       {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-05-new-config.md",
-          "redirect_url": "/azure/healthcare-apis/iot/deploy-new-config",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
           "redirect_document_id": false
       },
       {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-06-new-deploy.md",
-          "redirect_url": "/azure/healthcare-apis/iot/deploy-new-deploy",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
           "redirect_document_id": false
       },
       {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-08-new-ps-cli.md",
-          "redirect_url": "/azure/healthcare-apis/iot/deploy-new-powershell-cli",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-json-powershell-cli",
+          "redirect_document_id": false
+      },
+      {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-arm.md",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-arm-template",
           "redirect_document_id": false
       },
       {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-bicep-ps-cli.md",
-          "redirect_url": "/azure/healthcare-apis/iot/deploy-new-bicep-powershell-cli",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-bicep-powershell-cli",
           "redirect_document_id": false
-      }, 
+      },
+      {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-bicep-powershell-cli.md",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-bicep-powershell-cli",
+          "redirect_document_id": false
+      },
+      {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-choose.md",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-choose-method",
+          "redirect_document_id": false
+      },
+      {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-powershell-cli.md",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-json-powershell-cli",
+          "redirect_document_id": false
+      },
+      {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-config.md",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-manual-config",
+          "redirect_document_id": false
+      },
+      {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-deploy.md",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-manual-post",
+          "redirect_document_id": false
+      },
+      {   "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-manual.md",
+          "redirect_url": "/azure/healthcare-apis/iot/deploy-manual-prerequisites",
+          "redirect_document_id": false
+      },
       {   "source_path_from_root": "/articles/healthcare-apis/iot/iot-connector-overview.md",
           "redirect_url": "/azure/healthcare-apis/iot/overview",
           "redirect_document_id": false

.openpublishing.redirection.json

@@ -22562,6 +22562,11 @@
           "source_path_from_root": "/articles/azure-monitor/app/java-standalone-arguments.md",
           "redirect_url": "/azure/azure-monitor/app/java-get-started-supplemental",
           "redirect_document_id": true
+        },
+        {
+          "source_path_from_root": "/articles/healthcare-apis/dicom/dicom-cast-access-request.md",
+          "redirect_url": "/azure/healthcare-apis/dicom/dicom-cast-overview",
+          "redirect_document_id": false
         }
     ]
 }

articles/active-directory/app-provisioning/application-provisioning-log-analytics.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.subservice: app-provisioning
 ms.topic: conceptual
 ms.workload: identity
-ms.date: 10/06/2022
+ms.date: 04/25/2023
 ms.author: kenwith
 ms.reviewer: arvinh
 ---
@@ -19,7 +19,7 @@ Provisioning integrates with Azure Monitor logs and Log Analytics. With Azure mo
 
 ## Enabling provisioning logs
 
-You should already be familiar with Azure monitoring and Log Analytics. If not, jump over to learn about them and then come back to learn about application provisioning logs. To learn more about Azure monitoring, see [Azure Monitor overview](../../azure-monitor/overview.md). To learn more about Azure Monitor logs and Log Analytics, see [Overview of log queries in Azure Monitor](../../azure-monitor/logs/log-query-overview.md).
+You should already be familiar with Azure monitoring and Log Analytics. If not, jump over to learn about them, and then come back to learn about application provisioning logs. To learn more about Azure monitoring, see [Azure Monitor overview](../../azure-monitor/overview.md). To learn more about Azure Monitor logs and Log Analytics, see [Overview of log queries in Azure Monitor](../../azure-monitor/logs/log-query-overview.md).
 
 Once you've configured Azure monitoring, you can enable logs for application provisioning. The option is located on the **Diagnostics settings** page.
 
@@ -44,7 +44,7 @@ The underlying data stream that Provisioning sends log viewers is almost identic
 
 Azure Monitor workbooks provide a flexible canvas for data analysis. They also provide for the creation of rich visual reports within the Azure portal. To learn more, see [Azure Monitor Workbooks overview](../../azure-monitor/visualize/workbooks-overview.md).
 
-Application provisioning comes with a set of pre-built workbooks. You can find them on the Workbooks page. To view the data, you'll need to ensure that all the filters (timeRange, jobID, appName) are populated. You'll also need to make sure you've provisioned an app, otherwise there won't be any data in the logs.
+Application provisioning comes with a set of prebuilt workbooks. You can find them on the Workbooks page. To view the data, ensure that all the filters (timeRange, jobID, appName) are populated. Also confirm the app was provisioned, otherwise there isn't any data in the logs.
 
 :::image type="content" source="media/application-provisioning-log-analytics/workbooks.png" alt-text="Application provisioning workbooks" lightbox="media/application-provisioning-log-analytics/workbooks.png":::
 
@@ -108,7 +108,7 @@ Alert when there's a spike in disables or deletes.
 
 ## Community contributions
 
-We're taking an open source and community-based approach to application provisioning queries and dashboards. If you've built a query, alert, or workbook that you think others would find useful, be sure to publish it to the [AzureMonitorCommunity GitHub repo](https://github.com/microsoft/AzureMonitorCommunity). Then shoot us an email with a link. We'll review and publish it to the service so others can benefit too. You can contact us at [email protected].
+We're taking an open source and community-based approach to application provisioning queries and dashboards. Build a query, alert, or workbook that you think is useful to others, then publish it to the [AzureMonitorCommunity GitHub repo](https://github.com/microsoft/AzureMonitorCommunity). Shoot us an email with a link. We review and publish queries and dashboards to the service so others benefit too. Contact us at [email protected].
 
 ## Next steps
 

articles/active-directory/authentication/concept-fido2-hardware-vendor.md

@@ -53,7 +53,7 @@ The following table lists partners who are Microsoft-compatible FIDO2 security k
 | Nymi                      | ![y]              | ![n]| ![y]| ![n]| ![n]           | https://www.nymi.com/nymi-band                                                                      | 
 | Octatco                   | ![y]              | ![y]| ![n]| ![n]| ![n]           | https://octatco.com/                                                                                |
 | OneSpan Inc.              | ![n]              | ![y]| ![n]| ![y]| ![n]           | https://www.onespan.com/products/fido                                                               |
-| Swissbit                  | ![n]              | ![y]| ![y]| ![n]| ![n]           | https://www.swissbit.com/en/products/ishield-fido2/                                                 |
+| Swissbit                  | ![n]              | ![y]| ![y]| ![n]| ![n]           | https://www.swissbit.com/en/products/ishield-key/                                                 |
 | Thales Group              | ![n]              | ![y]| ![y]| ![n]| ![y]           | https://cpl.thalesgroup.com/access-management/authenticators/fido-devices                           |
 | Thetis                    | ![y]              | ![y]| ![y]| ![y]| ![n]           | https://thetis.io/collections/fido2                                                                 |
 | Token2 Switzerland        | ![y]              | ![y]| ![y]| ![n]| ![n]           | https://www.token2.swiss/shop/product/token2-t2f2-alu-fido2-u2f-and-totp-security-key               |

articles/active-directory/authentication/how-to-mfa-authenticator-lite.md

@@ -41,9 +41,6 @@ Users receive a notification in Outlook mobile to approve or deny sign-in, or th
 
 ## Enable Authenticator Lite
 
->[!NOTE]
->Rollout has not yet completed across Outlook applications. If this feature is enabled in your tenant, your users may not yet be prompted for the experience. To minimize user disruption, we recommend enabling this feature when the rollout completes.
-
 By default, Authenticator Lite is [Microsoft managed](concept-authentication-default-enablement.md#microsoft-managed-settings) and disabled during preview. After general availability, the Microsoft managed state default value will change to enable Authenticator Lite. 
 
 ### Enablement Authenticator Lite in Azure portal UX

articles/active-directory/cloud-infrastructure-entitlement-management/report-view-system-report.md

@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.subservice: ciem
 ms.workload: identity
 ms.topic: how-to
-ms.date: 02/23/2022
+ms.date: 04/24/2023
 ms.author: jfields
 ---
 
@@ -18,34 +18,43 @@ This article describes how to generate and view a system report in Permissions M
 
 ## Generate a system report
 
-1. In the Permissions Management home page, select the **Reports** tab, and then select the **Systems Reports** subtab.
+1. From the Permissions Management home page, select the **Reports** tab, and then select the **Systems Reports** subtab.
     The **Systems Reports** subtab displays the following options in the **Reports** table:
 
     - **Report Name**: The name of the report.
     - **Category**: The type of report: **Permission**.
-    - **Authorization System**: The authorization system activity in the report: Amazon Web Services (AWS), Microsoft Azure (Azure), and Google Cloud Platform (GCP).
+    - **Authorization System**: The cloud provider included in the report: Amazon Web Services (AWS), Microsoft Azure (Azure), and Google Cloud Platform (GCP).
     - **Format**: The format in which the report is available: comma-separated values (**CSV**) format, portable document format (**PDF**), or Microsoft Excel Open XML Spreadsheet (**XLSX**) format.
 
-1. In the **Report Name** column, find the report you want, and then select the down arrow to the right of the report name to download the report.
-
-    Or, from the ellipses **(...)** menu, select **Download**.
-
-    The following message displays: **Successfully Started To Generate On Demand Report.**
-
+1. In the **Report Name** column, find the report you want to generate.
+1. From the ellipses **(...)** menu for that report, select **Generate & Download**. A new window appears where you provide more information for the report you want to generate.
+1. For each **Authorization System**, select the **Authorization System Name** you want to include in the report by selecting the box next to the name. 
+1. If you want to combine all Authorization Systems into one report, check the box for **Collate**.
+1. For **Report Format**, check the boxes for a **Detailed** or **Summary** of the report in CSV format. You can select both. 
     > [!NOTE]
     > If you select one authorization system, the report includes a summary. If you select more than one authorization system, the report does not include a summary.
-
+1. For **Schedule**, select the frequency for how often you want to receive the report(s). You can select **None** if you don't want to generate reports on a scheduled basis.
+1. Click **Save**. Upon clicking **Save**, you receive a message **Report has been created**. The report appears on the **Custom Reports** tab.
 1. To refresh the list of reports, select **Reload**.
+1. On the **Custom Reports** tab, hover your mouse over the report, and click the down arrow to **Download** the report. A message appears **Successfully Started to Generate On Demand Report**. The report is sent to your email.
 
 ## Search for a system report
 
 1. On the **Systems Reports** subtab, select **Search**.
-1. In the **Search** box, enter the name of the report you want.
-
-    The **Systems Reports** subtab displays a list of reports that match your search criteria.
+1. In the **Search** box, enter the name of the report you want to locate. The **Systems Reports** subtab displays a list of reports that match your search criteria.
 1. Select a report from the **Report Name** column.
-1. To download a report, select the down arrow to the right of the report name, or from the ellipses **(...)** menu, select **Download**.
+1. To generate a report, click on the ellipses **(...)** menu for that report, then select **Generate & Download**. 
+1. For each **Authorization System**, select the **Authorization System Name** you want to include in the report by selecting the box next to the name. 
+1. If you want to combine all Authorization Systems into one report, check the box for **Collate**.
+1. For **Report Format**, check the boxes for a **Detailed** or **Summary** of the report in CSV format. You can select both. 
+
+    > [!NOTE]
+    > If you select one authorization system, the report includes a summary. If you select more than one authorization system, the report does not include a summary.
+1. For **Schedule**, select the frequency for how often you want to receive the report(s). You can select **None** if you don't want to generate reports on a scheduled basis.
+1. Click **Save**. Upon clicking **Save**, you receive a message **Report has been created**. The report appears on the **Custom Reports** tab.
 1. To refresh the list of reports, select **Reload**.
+1. On the **Custom Reports** tab, hover your mouse over the report, and click the down arrow to **Download** the report. A message appears **Successfully Started to Generate On Demand Report**. The report is sent to your email.
+ 
 
 
 ## Next steps

articles/active-directory/develop/msal-logging-dotnet.md

@@ -80,7 +80,7 @@ Example:
     {
         public EventLogLevel MinLogLevel { get; }
 
-        public TestIdentityLogger()
+        public MyIdentityLogger()
         {
             //Try to pull the log level from an environment variable
             var msalEnvLogLevel = Environment.GetEnvironmentVariable("MSAL_LOG_LEVEL");

articles/active-directory/enterprise-users/groups-bulk-download-members.md

@@ -5,7 +5,7 @@ services: active-directory
 author: barclayn
 ms.author: barclayn
 manager: amycolannino
-ms.date: 06/23/2022
+ms.date: 04/24/2023
 ms.topic: how-to
 ms.service: active-directory
 ms.subservice: enterprise-users
@@ -24,7 +24,7 @@ You can bulk download the members of a group in your organization to a comma-sep
 1. Sign in to [the Azure portal](https://portal.azure.com) with an account in the organization.
 1. In Azure AD, select **Groups** > **All groups**.
 1. Open the group whose membership you want to download, and then select **Members**.
-1. On the **Members** page, select **Download members** to download a CSV file listing the group members.
+1. On the **Members** page, select **Bulk operations** and choose, **Download members** to download a CSV file listing the group members.
 
    ![The Download Members command is on the profile page for the group](./media/groups-bulk-download-members/download-panel.png)