Merge pull request #224133 from MicrosoftDocs/main

1/17 AM Publish

Author: huypub

.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

@@ -33,16 +33,38 @@ If the original version of group writeback is already enabled and in use in your
 To configure directory settings to disable automatic writeback of newly created Microsoft 365 groups, use one of these methods:
 
 - Azure portal: Update the `NewUnifiedGroupWritebackDefault` setting to `false`. 
-- PowerShell: Use the [New-AzureADDirectorySetting](../enterprise-users/groups-settings-cmdlets.md) cmdlet. For example:
+- PowerShell: Use the [Microsoft Graph PowerShell SDK](/powershell/microsoftgraph/installation?view=graph-powershell-1.0&preserve-view=true). For example: 
 
   ```PowerShell 
-  $TemplateId = (Get-AzureADDirectorySettingTemplate | where {$_.DisplayName -eq "Group.Unified" }).Id 
-  $Template = Get-AzureADDirectorySettingTemplate | where -Property Id -Value $TemplateId -EQ 
-  $Setting = $Template.CreateDirectorySetting() 
-  $Setting["NewUnifiedGroupWritebackDefault"] = "False" 
-  New-AzureADDirectorySetting -DirectorySetting $Setting 
+    # Import Module
+    Import-Module Microsoft.Graph.Identity.DirectoryManagement
+
+    #Connect to MgGraph with necessary scope and select the Beta API Version
+    Connect-MgGraph -Scopes Directory.ReadWrite.All
+    Select-MgProfile -Name beta
+
+    # Import "Group.Unified" template values to a hashtable
+    $Template = Get-MgDirectorySettingTemplate | Where-Object {$_.DisplayName -eq "Group.Unified"}
+    $TemplateValues = @{}
+    $Template.Values | ForEach-Object {
+        $TemplateValues.Add($_.Name, $_.DefaultValue)
+    }
+
+    # Update the value for new unified group writeback default
+    $TemplateValues["NewUnifiedGroupWritebackDefault"] = "false"
+    # Create a directory setting using the Template values hashtable including the updated value
+    $params = @{}
+    $params.Add("TemplateId", $Template.Id)
+    $params.Add("Values", @())
+    $TemplateValues.Keys | ForEach-Object {
+        $params.Values += @(@{Name = $_; Value = $TemplateValues[$_]})
+    }
+    New-MgDirectorySetting -BodyParameter $params
   ``` 
 
+> [!NOTE]     
+> We recommend using Microsoft Graph PowerShell SDK with [Windows PowerShell 7](/powershell/scripting/whats-new/migrating-from-windows-powershell-51-to-powershell-7?view=powershell-7.3&preserve-view=true).
+
 - Microsoft Graph: Use the [directorySetting](/graph/api/resources/directorysetting?view=graph-rest-beta&preserve-view=true) resource type. 
 
 ### Disable writeback for all existing Microsoft 365 group 
@@ -56,7 +78,7 @@ To disable writeback of all Microsoft 365 groups that were created before these
     #Import-module
     Import-module Microsoft.Graph
 
-    #Connect to MgGraph and select the Beta API Version
+    #Connect to MgGraph with necessary scope and select the Beta API Version
     Connect-MgGraph -Scopes Group.ReadWrite.All
     Select-MgProfile -Name beta
 
@@ -68,8 +90,8 @@ To disable writeback of all Microsoft 365 groups that were created before these
     {
         Update-MgGroup -GroupId $group.id -WritebackConfiguration @{isEnabled=$false}
     }
-> We recomend using Microsoft Graph PowerShell SDK with [Windows PowerShell 7](/powershell/scripting/whats-new/migrating-from-windows-powershell-51-to-powershell-7?view=powershell-7.3&preserve-view=true)
-  
+  ```
+      
 - Microsoft Graph Explorer: Use a [group object](/graph/api/group-update?tabs=http&view=graph-rest-beta&preserve-view=true). 
 
 ## Delete groups when they're disabled for writeback or soft deleted 

articles/active-directory/hybrid/how-to-connect-modify-group-writeback.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: how-to
-ms.date: 11/21/2022
+ms.date: 01/10/2023
 ms.author: jeedes
 
 ---
@@ -31,7 +31,8 @@ To integrate Azure Active Directory with Digital Pigeon, you need:
 * An Azure AD user account. If you don't already have one, you can [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 * One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.
 * An Azure AD subscription. If you don't have a subscription, you can get a [free account](https://azure.microsoft.com/free/).
-* Digital Pigeon single sign-on (SSO) enabled subscription.
+* Digital Pigeon single sign-on (SSO) enabled subscription (i.e.: Business or Enterprise plans)
+* Digital Pigeon account owner access to the above subscription
 
 ## Add application and assign a test user
 
@@ -46,7 +47,8 @@ Add Digital Pigeon from the Azure AD application gallery to configure single sig
 Follow the guidelines in the [create and assign a user account](../manage-apps/add-application-portal-assign-users.md) article to create a test user account in the Azure portal called B.Simon.
 
    > [!NOTE]
-   > Please click [here](../develop/howto-add-app-roles-in-azure-ad-apps.md#app-roles-ui) to know how to configure Role in Azure AD. Role value is one of 'Digital Pigeon User', 'Digital Pigeon Power User', or 'Digital Pigeon Admin'. If role claim not supplied, default role is configurable in Digital Pigeon app by a Digital Pigeon Owner.
+   > Please click [here](../develop/howto-add-app-roles-in-azure-ad-apps.md#app-roles-ui) to learn how to configure App Roles in Azure AD. The Role value must be one of 'Digital Pigeon User', 'Digital Pigeon Power User', or 'Digital Pigeon Admin'. If a role claim is not supplied, the default role is configurable in the Digital Pigeon app (`Account Settings > SSO > SAML Provisioning Settings`) by a Digital Pigeon Owner, as seen below:
+   ![Screenshot shows how to configure SAML Provisioning Default Role.](media/digital-pigeon-tutorial/saml-default-role.png "SAML Default Role")
 
 Alternatively, you can also use the [Enterprise App Configuration Wizard](https://portal.office.com/AdminPortal/home?Q=Docs#/azureadappintegration). In this wizard, you can add an application to your tenant, add users/groups to the app, and assign roles. The wizard also provides a link to the single sign-on configuration pane in the Azure portal. [Learn more about Microsoft 365 wizards.](/microsoft-365/admin/misc/azure-ad-setup-guides). 
 
@@ -60,22 +62,25 @@ Complete the following steps to enable Azure AD single sign-on in the Azure port
 
    ![Screenshot shows to edit Basic SAML Configuration.](common/edit-urls.png "Basic Configuration")
 
-1. On the **Basic SAML Configuration** section, perform the following steps:
+1. In another browser tab, log in to Digital Pigeon as an account administrator.
 
-    a. In the **Identifier** textbox, type a URL using the following pattern:
-    `https://digitalpigeon.com/saml2/service-provider-metadata/<CustomerID>`
+1. Navigate to **Account Settings > SSO** and copy the **SP Entity ID** and **SP ACS URL** values.
 
-    b. In the **Reply URL** textbox, type a URL using the following pattern:
-    `https://digitalpigeon.com/login/saml2/sso/<CustomerID>`
+    ![Screenshot shows Digital Pigeon SAML Service Provider Settings.](media/digital-pigeon-tutorial/saml-service-provider-settings.png "SAML Service Provider Settings")
+
+1. Now in Azure AD, in the **Basic SAML Configuration** section, perform the following steps:
+
+    a. In the **Identifier** textbox, paste the value from _Digital Pigeon > Account Settings > SSO > **SP Entity ID**_.
+    It should match the following pattern: `https://digitalpigeon.com/saml2/service-provider-metadata/<CustomerID>`
+
+    b. In the **Reply URL** textbox, paste the value from _Digital Pigeon > Account Settings > SSO > **SP ACS URL**_.
+    It should match the following pattern: `https://digitalpigeon.com/login/saml2/sso/<CustomerID>`  
 
 1. Click **Set additional URLs** and perform the following step if you wish to configure the application in **SP** initiated mode:
 
     In the **Sign on URL** textbox, type the URL:
     `https://digitalpigeon.com/login`
 
-	> [!NOTE]
-	> These values are not real. Update these values with the actual Identifier and Reply URL. Contact [Digital Pigeon Client support team](mailto:[email protected]) to get these values. You can also refer to the patterns shown in the **Basic SAML Configuration** section in the Azure portal.
-
 1. Digital Pigeon application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
 
     ![Screenshot shows the image of attributes configuration.](common/default-attributes.png "Attributes")
@@ -91,13 +96,19 @@ Complete the following steps to enable Azure AD single sign-on in the Azure port
 
     ![Screenshot shows the Certificate download link.](common/metadataxml.png "Certificate")
 
-1. On the **Set up Digital Pigeon** section, copy the appropriate URL(s) based on your requirement.
+1. In Digital Pigeon, paste the content of downloaded **Federation Metadata XML** file into the **IDP Metadata XML** text field.
+
+    ![Screenshot shows IDP Metadata XML.](media/digital-pigeon-tutorial/idp-metadata-xml.png "IDP Metadata XML")
+
+1. In Azure AD, on the **Set up Digital Pigeon** section, copy the Azure AD Identifier URL.
 
 	![Screenshot shows to copy configuration appropriate U R L.](common/copy-configuration-urls.png "Metadata")
 
-## Configure Digital Pigeon SSO
+1. In Digital Pigeon, paste this URL into the **IDP Entity ID** text field.
+
+    ![Screenshot shows IDP Entity ID.](media/digital-pigeon-tutorial/idp-entity-id.png "IDP Entity ID")
 
-To configure single sign-on on **Digital Pigeon** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Digital Pigeon support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
+1. Click **Save** button to activate Digital Pigeon SSO.
 
 ### Create Digital Pigeon test user
 
@@ -121,6 +132,8 @@ You can also use Microsoft My Apps to test the application in any mode. When you
 
 ## Additional resources
 
+* Should you run into any issues or require additional support, please contact the [Digital Pigeon support team](mailto:[email protected])
+* For an alternative step-by-step guide, please refer to the Digital Pigeon KB article: [Azure AD SSO Configuration](https://digitalpigeon.zendesk.com/hc/en-us/articles/5403612403855-Azure-AD-SSO-Configuration)
 * [What is single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
 * [Plan a single sign-on deployment](../manage-apps/plan-sso-deployment.md).
 

articles/active-directory/saas-apps/digital-pigeon-tutorial.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 11/21/2022
+ms.date: 01/13/2023
 ms.author: jeedes
 ---
 # Tutorial: Azure AD SSO integration with Kintone
@@ -71,12 +71,8 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
 
 4. On the **Basic SAML Configuration** section, perform the following steps:
 
-    a. In the **Identifier (Entity ID)** text box, type a URL using one of the following patterns:
-	
-   | **Identifier** |
-   |---|
-   | `https://<companyname>.cybozu.com` |
-   | `https://<companyname>.kintone.com` |
+    a. In the **Identifier (Entity ID)** text box, type a URL using the following pattern:
+	`https://<companyname>.kintone.com`
 
     b. In the **Sign on URL** text box, type a URL using the following pattern:
     `https://<companyname>.kintone.com`