Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-troubleshooting-classic-admin-guest

Author: rolyon

.openpublishing.redirection.active-directory.json

@@ -55,6 +55,11 @@
       "redirect_url": "/azure/active-directory/saas-apps/tutorial-list",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/active-directory/saas-apps/trello-tutorial.md",
+      "redirect_url": "/azure/active-directory/saas-apps/atlassian-cloud-tutorial",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/active-directory/saas-apps/iauditor-tutorial.md",
       "redirect_url": "/azure/active-directory/saas-apps/safety-culture-tutorial",

.openpublishing.redirection.json

@@ -13241,7 +13241,7 @@
         },
         {
             "source_path_from_root": "/articles/logic-apps/logic-apps-monitor-your-logic-apps-oms.md",
-            "redirect_url": "/azure/logic-apps/monitor-logic-apps-log-analytics",
+            "redirect_url": "/azure/logic-apps/monitor-workflows-collect-diagnostic-data",
             "redirect_document_id": false
         },
         {
@@ -13339,6 +13339,12 @@
             "redirect_url": "/connectors/custom-connectors/submit-certification",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/logic-apps/monitor-logic-apps-log-analytics.md",
+            "redirect_url": "/azure/logic-apps/monitor-workflows-collect-diagnostic-data",
+            "redirect_document_id": true
+        },
+
         {
             "source_path_from_root": "/articles/connectors/connectors-create-api-sharepointonline.md",
             "redirect_url": "/azure/connectors/connectors-create-api-sharepoint",

articles/active-directory-b2c/identity-provider-generic-saml-options.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
-ms.date: 01/13/2022
+ms.date: 02/17/2023
 ms.custom: project-no-code
 ms.author: godonnell
 ms.subservice: B2C
@@ -294,7 +294,7 @@ The following SAML authorization request contains the authentication context cla
 
 ## Include custom data in the authorization request
 
-You can optionally include protocol message extension elements that are agreed to by both Azure AD BC and your identity provider. The extension is presented in XML format. You include extension elements by adding XML data inside the CDATA element `<![CDATA[Your Custom XML]]>`. Check your identity provider’s documentation to see if the extensions element is supported.
+You can optionally include protocol message extension elements that are agreed to by both Azure AD B2C and your identity provider. The extension is presented in XML format. You include extension elements by adding XML data inside the CDATA element `<![CDATA[Your Custom XML]]>`. Check your identity provider’s documentation to see if the extensions element is supported.
 
 The following example illustrates the use of extension data:
 

articles/active-directory/app-provisioning/media/provisioning-workbook/details-1.png

@@ -0,0 +1,143 @@
+---
+title: 'Provisioning insights workbook'
+description: This article describes the Azure Monitor workbook for provisioning.
+services: active-directory
+author: billmath
+manager: amycolannino
+ms.service: active-directory
+ms.topic: conceptual
+ms.workload: identity
+ms.date: 02/17/2023
+ms.subservice: hybrid
+ms.author: billmath
+ms.collection: M365-identity-device-management
+---
+
+
+
+# Provisioning insights workbook
+The Provisioning workbook provides a flexible canvas for data analysis. This workbook brings together all of the provisioning logs from various sources and allows you to gain insight, in a single area.  The workbook allows you to create rich visual reports within the Azure portal. To learn more, see Azure Monitor Workbooks overview.
+
+This workbook is intended for Hybrid Identity Admins who use provisioning to sync users from various data sources to various data repositories.  It allows admins to gain insights into sync status and details.
+
+This workbook:
+
+- Provides a synchronization summary of users and groups synchronized from all of you provisioning sources to targets
+- Provides and aggregated and detailed view of information captured by the provisioning logs.
+- Allows you to customize the data to tailor it to your specific needs
+
+
+
+## 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) and [Provisioning Logs for troubleshooting cloud sync](../cloud-sync/how-to-troubleshoot.md).
+
+## Source and Target
+At the top of the workbook, using the drop-down, specify the source and target identities.  
+
+Theses fields are the source and target of identities.  The rest of the filters that appear are based on the selection of source and target.
+You can scope your search so that it is more granular using the additional fields.  Use the table below as a reference for queries.
+
+For example, if you wanted to see data from your cloud sync workflow, your source would be Active Directory and your target would be Azure AD.
+
+
+>[!NOTE]
+>Source and target are required.  If you do not select a source and target, you won't see any data.
+
+:::image type="content" source="media/provisioning-workbook/fields-1.png" alt-text="Screenshot of fields." lightbox="media/provisioning-workbook/fields-1.png":::
+
+
+|Field|Description|
+|-----|-----|
+|Source|The provisioning source repository|
+|Target|The provisioning target repository|
+|Time Range|The range of provisioning information you want to view.  This can be anywhere from 4 hours to 90 days.  You can also set a custom value.|
+|Status|View the provisioning status such as Success or Skipped.|
+|Action|View the provisioning actions taken such as Create or Delete.|
+|App Name|Allows you to filter by the application name.  In the case of Active Directory, you can filter by domains.|
+|Job Id|Allows you to target specific Job Ids.|
+|Sync type|Filter by type of synchronization such as object or password.|
+
+>[!NOTE]
+> All of the charts and grids in Sync Summary, Sync Details, and Sync Details by grid, change based on source,target and the parameter selections. 
+
+
+## Sync Summary  
+The sync summary section provides a summary of your organizations synchronization activities.  These activities include:
+   - Total synced objects by type 
+   - Provisioning events by action
+   - Provisioning events by status
+   - Unique sync count by status
+   - Provisioning success rate
+   - Top provisioning errors
+
+
+ :::image type="content" source="media/provisioning-workbook/sync-summary-1.png" alt-text="Screenshot of the synchronization summary." lightbox="media/provisioning-workbook/sync-summary-1.png":::
+
+## Sync details
+The sync details tab allows you to drill into the synchronization data and get more information.  This information includes:
+   - Objects sync by status
+   - Objects synced by action
+   - Sync log details
+   
+ >[!NOTE] 
+ >The grid is filterable on any of the above filters but you can also click the tiles under under **Objects synced by Status** and **Action**.
+ 
+ :::image type="content" source="media/provisioning-workbook/sync-details-1.png" alt-text="Screenshot of the synchronization details." lightbox="media/provisioning-workbook/sync-details-1.png":::
+
+You can further drill in to the sync log details for additional information.
+
+
+
+>[!NOTE]
+>Clicking on the Source ID it will dive deeper and provide more information on the synchronized object.
+ 
+## Sync details by cycle
+The sync details by cycle tab allow you to get more granular with the synchronization data.  This information includes:
+   - Objects sync by status
+   - Objects synced by action
+   - Sync log details
+ 
+ :::image type="content" source="media/provisioning-workbook/sync-details-2.png" alt-text="Screenshot of the synchronization details by cycle tab." lightbox="media/provisioning-workbook/sync-details-2.png":::
+
+You can further drill in to the sync log details for additional information.
+
+>[!NOTE] 
+>The grid is filterable on any of the above filters but you can also click the tiles under under **Objects synced by Status** and **Action**.
+
+## Single user view
+The user provisioning view tab allows you to get synchronization data on individual users.  
+
+>[!NOTE]
+>This section does not involve using source and target.  
+
+In this section, you enter a time range and select a specific user to see which applications a user has been provisioned or deprovisioned in.
+
+Once you select a time range, it will filter for users that have events in that time range.
+
+
+To target a specific user, you can add one of the following parameters, for that user. 
+   - UPN
+   - UserID
+   
+:::image type="content" source="media/provisioning-workbook/single-user-1.png" alt-text="Screenshot of the single user view." lightbox="media/provisioning-workbook/single-user-1.png":::
+ 
+## Details 
+By clicking on the Source ID in the  **Sync details** or the **Sync details by cycle** views, you can see additional information on the object synchronized.
+
+:::image type="content" source="media/provisioning-workbook/details-1.png" alt-text="Screenshot of the details of an object." lightbox="media/provisioning-workbook/details-1.png":::
+
+## Custom queries
+
+You can create custom queries and show the data on Azure dashboards. To learn how, see [Create and share dashboards of Log Analytics data](../../azure-monitor/logs/get-started-queries.md). Also, be sure to check out [Overview of log queries in Azure Monitor](../../azure-monitor/logs/log-query-overview.md).
+
+## Custom alerts
+
+Azure Monitor lets you configure custom alerts so that you can get notified about key events related to Provisioning. For example, you might want to receive an alert on spikes in failures. Or perhaps spikes in disables or deletes. Another example of where you might want to be alerted is a lack of any provisioning, which indicates something is wrong.
+
+To learn more about alerts, see [Azure Monitor Log Alerts](../../azure-monitor/alerts/alerts-log.md).
+
+## Next steps 
+
+- [What is provisioning?](../cloud-sync/what-is-provisioning.md)
+- [Error codes](../cloud-sync/reference-error-codes.md)