Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Banani-Rath

.openpublishing.redirection.azure-monitor.json

@@ -1,5 +1,41 @@
 {
     "redirections": [
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/snapshot-debugger.md",
+            "redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/snapshot-debugger-vm.md",
+            "redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger-vm",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/snapshot-debugger-upgrade.md",
+            "redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger-upgrade",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/snapshot-debugger-troubleshoot.md",
+            "redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger-troubleshoot",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/snapshot-debugger-function-app.md",
+            "redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger-function-app",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/snapshot-debugger-appservice.md",
+            "redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger-appservice",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/app/snapshot-debugger-release-notes.md",
+            "redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger-release-notes",
+            "redirect_document_id": false
+        },
+
         {
             "source_path_from_root": "/articles/azure-monitor/app/profiler.md",
             "redirect_url": "/azure/azure-monitor/profiler/profiler",

.openpublishing.redirection.json

@@ -749,6 +749,11 @@
       "redirect_url": "/azure/frontdoor/how-to-configure-endpoints",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/frontdoor/standard-premium/create-front-door-cli.md",
+      "redirect_url": "/azure/frontdoor/create-front-door-cli",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/app-service-web/web-sites-dotnet-deploy-aspnet-mvc-app-membership-oauth-sql-database.md",
       "redirect_url": "/aspnet/core/security/authorization/secure-data",

articles/active-directory/app-provisioning/hr-attribute-retrieval-issues.md

@@ -13,27 +13,35 @@ ms.reviewer: chmutali
 ---
 # Troubleshoot HR attribute retrieval issues
 
-## Provisioning app is not fetching all Workday attributes
-**Applies to:**
-* Workday to on-premises Active Directory user provisioning
-* Workday to Azure Active Directory user provisioning
-
-| Troubleshooting | Details |
-|-- | -- |
-| **Issue** | You have just setup the Workday inbound provisioning app and successfully connected to the Workday tenant URL. You ran a test sync and you observed that the provisioning app is not retrieving all attributes from Workday. Only some attributes are read and provisioned to the target. |
-| **Cause** | By default, the Workday provisioning app ships with attribute mapping and XPATH definitions that work with Workday Web Services (WWS) v21.1. When configuring connectivity to Workday in the provisioning app, if you explicitly specified the WWS API version (example: `https://wd3-impl-services1.workday.com/ccx/service/contoso4/Human_Resources/v34.0`), then you may run into this issue, because of the mismatch between WWS API version and the XPATH definitions.  |
-| **Resolution** | * *Option 1*: Remove the WWS API version information from the URL and use the default WWS API version v21.1 <br> * *Option 2*: Manually update the XPATH API expressions so it is compatible with your preferred WWS API version. Update the **XPATH API expressions** under **Attribute Mapping -> Advanced Options -> Edit attribute list for Workday** referring to the section [Workday attribute reference](../app-provisioning/workday-attribute-reference.md#xpath-values-for-workday-web-services-wws-api-v30)  |
-
-## Provisioning app is not fetching Workday integration system attributes / calculated fields
-**Applies to:**
-* Workday to on-premises Active Directory user provisioning
-* Workday to Azure Active Directory user provisioning
-
-| Troubleshooting | Details |
-|-- | -- |
-| **Issue** | You have just setup the Workday inbound provisioning app and successfully connected to the Workday tenant URL. You have an integration system configured in Workday and you have configured XPATHs that point to attributes in the Workday Integration System. However, the Azure AD provisioning app is not fetching values associated with these integration system attributes or calculated fields. |
-| **Cause** | This is a known limitation. The Workday provisioning app currently does not support fetching calculated fields/integration system attributes.  |
-| **Resolution** | There is no workaround for this limitation. |
+## Issue fetching Workday attributes
+
+
+| **Applies to** |
+|--|
+| * Workday to on-premises Active Directory user provisioning <br> * Workday to Azure Active Directory user provisioning |
+| **Issue Description** | 
+| You have just configured the Workday inbound provisioning app and successfully connected to the Workday tenant URL. You ran a test sync and you observed that the provisioning app is not retrieving certain attributes from Workday. Only some attributes are read and provisioned to the target. |
+| **Probable Cause** | 
+| By default, the Workday provisioning app ships with attribute mapping and XPATH definitions that work with Workday Web Services (WWS) v21.1. When configuring connectivity to Workday in the provisioning app, if you explicitly specified the WWS API version (example: `https://wd3-impl-services1.workday.com/ccx/service/contoso4/Human_Resources/v34.0`), then you may run into this issue, because of the mismatch between WWS API version and the XPATH definitions.  |
+| **Resolution Options** | 
+| * *Option 1*: Remove the WWS API version information from the URL and use the default WWS API version v21.1 <br> * *Option 2*: Manually update the XPATH API expressions so it is compatible with your preferred WWS API version. Update the **XPATH API expressions** under **Attribute Mapping -> Advanced Options -> Edit attribute list for Workday** referring to the section [Workday attribute reference](../app-provisioning/workday-attribute-reference.md#xpath-values-for-workday-web-services-wws-api-v30)  |
+
+## Issue fetching Workday calculated fields
+
+| **Applies to** |
+|--|
+| * Workday to on-premises Active Directory user provisioning <br> * Workday to Azure Active Directory user provisioning |
+| **Issue Description** | 
+| You have just configured the Workday inbound provisioning app and successfully connected to the Workday tenant URL. You have an integration system configured in Workday and you have configured XPATHs that point to attributes in the Workday Integration System. However, the Azure AD provisioning app isn't fetching values associated with these integration system attributes or calculated fields. |
+| **Cause** | 
+| This is a known limitation. The Workday provisioning app currently doesn't support fetching calculated fields/integration system attributes using the *Field_And_Parameter_Criteria_Data* Get_Workers request filter.  |
+| **Resolution Options** | 
+| You could consider a workaround of either using Workday Provisioning groups or Workday Custom ID field. See details below. |
+
+**Suggested workarounds**
+ * **Option 1: Using Workday Provisioning Groups**: Check if the calculated field value can be represented as a provisioning group in Workday. Using the same logic that is used for the calculated field, your Workday Admin may be able to assign a Provisioning Group to the user. Reference Workday doc that requires Workday login: [Set Up Account Provisioning Groups](https://doc.workday.com/reader/3DMnG~27o049IYFWETFtTQ/keT9jI30zCzj4Nu9pJfGeQ). Once configured, this Provisioning Group assignment can be [retrieved in the provisioning job](../app-provisioning/workday-integration-reference.md#example-3-retrieving-provisioning-group-assignments) and used in attribute mappings and scoping filter. 
+* **Option 2: Using Workday Custom IDs**: Check if the calculated field value can be represented as a Custom ID on the Worker Profile. Use `Maintain Custom ID Type` task in Workday to define a new type and populate values in this custom ID. Make sure the [Workday ISU account used for the integration](../saas-apps/workday-inbound-tutorial.md#configuring-domain-security-policy-permissions) has domain security permission for `Person Data: ID Information`. For example, you can define "External_Payroll_ID" as a custom ID in Workday and retrieved it using the XPATH: `wd:Worker/wd:Worker_Data/wd:Personal_Data/wd:Identification_Data/wd:Custom_ID/wd:Custom_ID_Data[wd:ID_Type_Reference/wd:ID[@wd:type=\"Custom_ID_Type_ID\"]=\"External_Payroll_ID\"]/wd:ID/text()`
+
 
 ## Next steps
 

articles/active-directory/app-proxy/application-proxy-add-on-premises-application.md

@@ -15,7 +15,7 @@ ms.reviewer: ashishj
 
 # Tutorial: Add an on-premises application for remote access through Application Proxy in Azure Active Directory
 
-Azure Active Directory (Azure AD) has an Application Proxy service that enables users to access on-premises applications by signing in with their Azure AD account. To learn more about Application Proxy, see [What is App Proxy?](what-is-application-proxy.md). This tutorial prepares your environment for use with Application Proxy. Once your environment is ready, you'll use the Azure portal to add an on-premises application to your Azure AD tenant. 
+Azure Active Directory (Azure AD) has an Application Proxy service that enables users to access on-premises applications by signing in with their Azure AD account. To learn more about Application Proxy, see [What is App Proxy?](what-is-application-proxy.md). This tutorial prepares your environment for use with Application Proxy. Once your environment is ready, you'll use the Azure portal to add an on-premises application to your Azure AD tenant.
 
 :::image type="content" source="./media/application-proxy-add-on-premises-application/app-proxy-diagram.png" alt-text="Application Proxy Overview Diagram" lightbox="./media/application-proxy-add-on-premises-application/app-proxy-diagram.png":::
 
@@ -53,7 +53,7 @@ For high availability in your production environment, we recommend having more t
 >
 > ```
 > Windows Registry Editor Version 5.00
-> 
+>
 > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
 > "EnableDefaultHTTP2"=dword:00000000
 > ```
@@ -155,7 +155,7 @@ To install the connector:
 1. Read the Terms of Service. When you're ready, select **Accept terms & Download**.
 1. At the bottom of the window, select **Run** to install the connector. An install wizard opens.
 1. Follow the instructions in the wizard to install the service. When you're prompted to register the connector with the Application Proxy for your Azure AD tenant, provide your application administrator credentials.
-   
+
     - For Internet Explorer (IE), if **IE Enhanced Security Configuration** is set to **On**, you may not see the registration screen. To get access, follow the instructions in the error message. Make sure that **Internet Explorer Enhanced Security Configuration** is set to **Off**.
 
 ### General remarks
@@ -166,7 +166,7 @@ If you choose to have more than one Windows server for your on-premises applicat
 
 If you have installed connectors in different regions, you can optimize traffic by selecting the closest Application Proxy cloud service region to use with each connector group, see [Optimize traffic flow with Azure Active Directory Application Proxy](application-proxy-network-topology.md)
 
-If your organization uses proxy servers to connect to the internet, you need to configure them for Application Proxy.  For more information, see [Work with existing on-premises proxy servers](./application-proxy-configure-connectors-with-proxy-servers.md). 
+If your organization uses proxy servers to connect to the internet, you need to configure them for Application Proxy.  For more information, see [Work with existing on-premises proxy servers](./application-proxy-configure-connectors-with-proxy-servers.md).
 
 For information about connectors, capacity planning, and how they stay up-to-date, see [Understand Azure AD Application Proxy connectors](application-proxy-connectors.md).
 
@@ -201,12 +201,12 @@ To confirm the connector installed and registered correctly:
 
 ## Add an on-premises app to Azure AD
 
-Now that you've prepared your environment and installed a connector, you're ready to add on-premises applications to Azure AD.  
+Now that you've prepared your environment and installed a connector, you're ready to add on-premises applications to Azure AD.
 
 1. Sign in as an administrator in the [Azure portal](https://portal.azure.com/).
 2. In the left navigation panel, select **Azure Active Directory**.
 3. Select **Enterprise applications**, and then select **New application**.
-4. Select **Add an on-premises application** button which appears about halfway down the page in the **On-premises applications** section. Alternatively, you can select **Create your own application** at the top of the page and then select **Configure Application Proxy for secure remote access to an on-premise application**.
+4. Select **Add an on-premises application** button which appears about halfway down the page in the **On-premises applications** section. Alternatively, you can select **Create your own application** at the top of the page and then select **Configure Application Proxy for secure remote access to an on-premises application**.
 5. In the **Add your own on-premises application** section, provide the following information about your application:
 
     | Field  | Description |
@@ -217,7 +217,7 @@ Now that you've prepared your environment and installed a connector, you're read
     | **Pre Authentication** | How Application Proxy verifies users before giving them access to your application.<br><br>**Azure Active Directory** - Application Proxy redirects users to sign in with Azure AD, which authenticates their permissions for the directory and application. We recommend keeping this option as the default so that you can take advantage of Azure AD security features like Conditional Access and Multi-Factor Authentication. **Azure Active Directory** is required for monitoring the application with Microsoft Cloud Application Security.<br><br>**Passthrough** - Users don't have to authenticate against Azure AD to access the application. You can still set up authentication requirements on the backend. |
     | **Connector Group** | Connectors process the remote access to your application, and connector groups help you organize connectors and apps by region, network, or purpose. If you don't have any connector groups created yet, your app is assigned to **Default**.<br><br>If your application uses WebSockets to connect, all connectors in the group must be version 1.5.612.0 or later. |
 
-6. If necessary, configure **Additional settings**. For most applications, you should keep these settings in their default states. 
+6. If necessary, configure **Additional settings**. For most applications, you should keep these settings in their default states.
 
     | Field | Description |
     | :------------------------------ | :----------------------------------------------------------- |

articles/active-directory/authentication/howto-authentication-passwordless-faqs.md

@@ -156,7 +156,7 @@ On a Windows Server 2016 or 2019 domain controller, check that the following pat
 
 ### Can I deploy the FIDO2 credential provider on an on-premises only device?
 
-No, this feature isn't supported for on-premise only device. The FIDO2 credential provider wouldn't show up.
+No, this feature isn't supported for on-premises only device. The FIDO2 credential provider wouldn't show up.
 
 ### FIDO2 security key sign-in isn't working for my Domain Admin or other high privilege accounts. Why?
 

articles/active-directory/cloud-infrastructure-entitlement-management/faqs.md

@@ -122,7 +122,8 @@ Yes, Permissions Management has various types of system report available that ca
 
 For information about permissions usage reports, see [Generate and download the Permissions analytics report](product-permissions-analytics-reports.md).
 
-## Does Permissions Management integrate with third-party ITSM (Information Technology Security Management) tools?
+
+## Does Permissions Management integrate with third-party ITSM (Information Technology Service Management) tools?
 
 Permissions Management integrates with ServiceNow.