Merge pull request #175162 from MicrosoftDocs/master

10/08 PM Publish

Author: huypub

CODEOWNERS

@@ -3,87 +3,84 @@
 # Horizontals
 
 ## Azure Policy: Samples and Compliance Controls
-articles/**/policy-reference.md @DCtheGeek
-articles/**/security-controls-policy.md @DCtheGeek
-includes/policy/ @DCtheGeek
+/articles/**/policy-reference.md @DCtheGeek
+/articles/**/security-controls-policy.md @DCtheGeek
+/includes/policy/ @DCtheGeek
 
 # Azure Monitor
-
-articles/azure-monitor/* @bwren
-articles/azure-monitor/agents @bwren
-articles/azure-monitor/alerts @rboucher
-articles/azure-monitor/app @bwren @lgayhardt
-articles/azure-monitor/autoscale @rboucher
-articles/azure-monitor/containers @bwren
-articles/azure-monitor/essentials @bwren @rboucher
-articles/azure-monitor/insights @bwren @rboucher @lgayhardt
-articles/azure-monitor/logs @bwren
-articles/azure-monitor/visualize @bwren @lgayhardt
-articles/azure-monitor/vm @bwren
-articles/advisor @rboucher
-articles/service-health @rboucher
+/articles/azure-monitor/* @bwren
+/articles/azure-monitor/agents @bwren
+/articles/azure-monitor/alerts @rboucher
+/articles/azure-monitor/app @bwren @lgayhardt
+/articles/azure-monitor/autoscale @rboucher
+/articles/azure-monitor/containers @bwren
+/articles/azure-monitor/essentials @bwren @rboucher
+/articles/azure-monitor/insights @bwren @rboucher @lgayhardt
+/articles/azure-monitor/logs @bwren
+/articles/azure-monitor/visualize @bwren @lgayhardt
+/articles/azure-monitor/vm @bwren
+/articles/advisor @rboucher
+/articles/service-health @rboucher
 
 # Azure Active Directory
-
-articles/active-directory-b2c/ @msmimart @yoelhor
-articles/active-directory/app-provisioning/ @CelesteDG
-articles/active-directory/develop/ @mmacy
-articles/active-directory/manage-apps/ @CelesteDG
+/articles/active-directory-b2c/ @msmimart @yoelhor
+/articles/active-directory/app-provisioning/ @CelesteDG
+/articles/active-directory/develop/ @mmacy
+/articles/active-directory/manage-apps/ @CelesteDG
 
 # Azure Synapse Analytics
-articles/synapse-analytics/ @julieMSFT [email protected] @ryanmajidi @saveenr 
-articles/synapse-analytics/backuprestore/ @joannapea @julieMSFT
-articles/synapse-analytics/catalog-governance/@djpmsft @chanuengg 
-articles/synapse-analytics/ccid/ @liudan66 @julieMSFT
-articles/synapse-analytics/data-integration/ @kromerm @jonburchel 
-articles/synapse-analytics/machine-learning/ @garyericson @NelGson @midesa 
-articles/synapse-analytics/metadata/@MikeRys @julieMSFT @jocaplan
-articles/synapse-analytics/security/ @RonyMSFT  @nanditavalsan @meenalsri @julieMSFT
-articles/synapse-analytics/spark/ @euangms @mlee3gsd @midesa 
-articles/synapse-analytics/sql/ @filippopovic @azaricstefan @anumjs @WilliamDAssafMSFT @jovanpop-msft
-articles/synapse-analytics/sql-data-warehouse/ @anumjs @ronortloff @julieMSFT
-articles/synapse-analytics/synapse-link/ @Rodrigossz @SnehaGunda @jovanpop-msft
+/articles/synapse-analytics/ @julieMSFT @ryanmajidi @saveenr 
+/articles/synapse-analytics/backuprestore/ @joannapea @julieMSFT
+/articles/synapse-analytics/catalog-governance/@djpmsft @chanuengg 
+/articles/synapse-analytics/ccid/ @liudan66 @julieMSFT
+/articles/synapse-analytics/data-integration/ @kromerm @jonburchel 
+/articles/synapse-analytics/machine-learning/ @garyericson @NelGson @midesa 
+/articles/synapse-analytics/metadata/@MikeRys @julieMSFT @jocaplan
+/articles/synapse-analytics/security/ @RonyMSFT  @nanditavalsan @meenalsri @julieMSFT
+/articles/synapse-analytics/spark/ @euangms @mlee3gsd @midesa 
+/articles/synapse-analytics/sql/ @filippopovic @azaricstefan @anumjs @WilliamDAssafMSFT @jovanpop-msft
+/articles/synapse-analytics/sql-data-warehouse/ @anumjs @ronortloff @julieMSFT
+/articles/synapse-analytics/synapse-link/ @Rodrigossz @SnehaGunda @jovanpop-msft
 
 # Cognitive Services
-articles/cognitive-services/ @aahill @patrickfarley @nitinme @mrbullwinkle @laujan
+/articles/cognitive-services/ @aahill @patrickfarley @nitinme @mrbullwinkle @laujan
 
 # DevOps
-articles/ansible/ @TomArcherMsft
-articles/chef/ @TomArcherMsft
-articles/jenkins/ @TomArcherMsft
-articles/terraform/ @TomArcherMsft
+/articles/ansible/ @TomArcherMsft
+/articles/chef/ @TomArcherMsft
+/articles/jenkins/ @TomArcherMsft
+/articles/terraform/ @TomArcherMsft
 
 # compute
-articles/virtual-machines/ @cynthn @mimckitt
-articles/virtual-machine-scale-sets/ @ju-shim @mimckitt
-articles/cloud-services/ @mimckitt
-articles/cloud-services-extended-support/ @mimckitt
-articles/service-fabric/ @sukanyamsft @mimckitt
-articles/container-instances/ @macolso @mimckitt
-articles/container-registry/ @dlepow @mimckitt
+/articles/virtual-machines/ @cynthn @mimckitt
+/articles/virtual-machine-scale-sets/ @ju-shim @mimckitt
+/articles/cloud-services/ @mimckitt
+/articles/cloud-services-extended-support/ @mimckitt
+/articles/service-fabric/ @sukanyamsft @mimckitt
+/articles/container-instances/ @macolso @mimckitt
+/articles/container-registry/ @dlepow @mimckitt
 
 # Requires Internal Review
-articles/best-practices-availability-paired-regions.md @martinekuan @syntaxc4 @snoviking
+/articles/best-practices-availability-paired-regions.md @martinekuan @syntaxc4 @snoviking
 
 # Governance
-articles/governance/ @DCtheGeek
+/articles/governance/ @DCtheGeek
 
 # Security
-articles/security/fundamentals/feature-availability.md @msmbaldwin @terrylanfear
+/articles/security/fundamentals/feature-availability.md @msmbaldwin @terrylanfear
 
 # Azure Security Center
-articles/security-center/ @memildin
-includes/*security-controls*.md @memildin
+/articles/security-center/ @memildin
+/includes/*security-controls*.md @memildin
 
 # DDOS Protection
-
-articles/ddos-protection @aletheatoh @anupamvi
+/articles/ddos-protection @aletheatoh @anupamvi
 
 # Lighthouse
-articles/lighthouse/ @JnHs
+/articles/lighthouse/ @JnHs
 
 # Healthcare APIs
-articles/healthcare-apis/ @ginalee-dotcom
+/articles/healthcare-apis/ @ginalee-dotcom
 
 # Configuration
 *.json @SyntaxC4 @snoviking @martinekuan

articles/active-directory-b2c/extensions-app.md

@@ -32,11 +32,11 @@ To verify that the b2c-extensions-app is present:
 
 If you accidentally deleted the b2c-extensions-app, you have 30 days to recover it. You can restore the app using the Graph API:
 
-1. Browse to [https://graphexplorer.azurewebsites.net/](https://graphexplorer.azurewebsites.net/).
+1. Browse to [https://developer.microsoft.com/en-us/graph/graph-explorer](https://developer.microsoft.com/en-us/graph/graph-explorer).
 1. Log in to the site as a global administrator for the Azure AD B2C directory that you want to restore the deleted app for. This global administrator must have an email address similar to the following: `username@{yourTenant}.onmicrosoft.com`.
-1. Issue an HTTP GET against the URL `https://graph.windows.net/myorganization/deletedApplications` with api-version=1.6. This operation will list all of the applications that have been deleted within the past 30 days.
+1. Issue an HTTP GET against the URL `https://graph.microsoft.com/beta/directory/deleteditems/microsoft.graph.application`. This operation will list all of the applications that have been deleted within the past 30 days.
 1. Find the application in the list where the name begins with 'b2c-extensions-app’ and copy its `objectid` property value.
-1. Issue an HTTP POST against the URL `https://graph.windows.net/myorganization/deletedApplications/{OBJECTID}/restore`. Replace the `{OBJECTID}` portion of the URL with the `objectid` from the previous step.
+1. Issue an HTTP POST against the URL `https://graph.microsoft.com/beta/directory/deleteditems/{id}/restore`. Replace the `{OBJECTID}` portion of the URL with the `objectid` from the previous step.
 
 You should now be able to [see the restored app](#verifying-that-the-extensions-app-is-present) in the Azure portal.
 

articles/active-directory-domain-services/faqs.yml

@@ -11,7 +11,7 @@ metadata:
   ms.subservice: domain-services
   ms.workload: identity
   ms.topic: how-to
-  ms.date: 09/01/2021
+  ms.date: 10/08/2021
   ms.author: justinha
 
 title: Frequently asked questions (FAQs) about Azure Active Directory (AD) Domain Services
@@ -86,9 +86,9 @@ sections:
           No. A managed domain resource forest supports up to five one-way outbound forest trusts to on-premises forests. 
 
       - question: |
-          Can I move an existing Azure AD Domain Services managed domain to a different subscription, resource group, region, virtual network, or subnet?
+          Can I move a managed domain?
         answer: |
-          No. After you create an Azure AD Domain Services managed domain, you can't then move the managed domain to a different subscription, resource group, region, virtual network, or subnet. Take care to select the most appropriate subscription, resource group, region, virtual network, and subnet when you deploy the managed domain.
+          No. After you create an Azure AD Domain Services managed domain, you can't move it to a different subscription, resource group, region, virtual network, or subnet. As a workaround, you can [delete the managed domain](delete-aadds.md) by using PowerShell or the Azure portal and re-create it with your desired setup. No restore operations can be provided while the managed domain is re-created.
 
       - question: |
           Can I rename an existing Azure AD Domain Services domain name?

articles/active-directory/saas-apps/directprint-io-provisioning-tutorial.md

@@ -0,0 +1,151 @@
+---
+title: 'Tutorial: Configure directprint.io for automatic user provisioning with Azure Active Directory | Microsoft Docs'
+description: Learn how to automatically provision and de-provision user accounts from Azure AD to directprint.io.
+services: active-directory
+documentationcenter: ''
+author: twimmer
+writer: Thwimmer
+manager: beatrizd
+
+ms.assetid: 0a79e880-bbdf-45e4-ae1e-2c74aec9f51e
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.tgt_pltfrm: na
+ms.devlang: na
+ms.topic: article
+ms.date: 09/24/2021
+ms.author: Thwimmer
+---
+
+# Tutorial: Configure directprint.io for automatic user provisioning
+
+This tutorial describes the steps you need to perform in both directprint.io and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users and groups to [directprint.io](https://directprint.io) using the Azure AD provisioning service. For important details on what this service does, how it works, and frequently asked questions, see [Automate user provisioning and deprovisioning to SaaS applications with Azure Active Directory](../app-provisioning/user-provisioning.md). 
+
+
+## Capabilities supported
+> [!div class="checklist"]
+> * Create users in directprint.io.
+> * Remove users in directprint.io when they do not require access anymore.
+> * Keep user attributes synchronized between Azure AD and directprint.io.
+> * Provision groups and group memberships in directprint.io.
+> * [Single sign-on](directprint-io-cloud-print-administration-tutorial.md) to directprint.io (recommended).
+
+## Prerequisites
+
+The scenario outlined in this tutorial assumes that you already have the following prerequisites:
+
+* [An Azure AD tenant](../develop/quickstart-create-new-tenant.md). 
+* A user account in Azure AD with [permission](../roles/permissions-reference.md) to configure provisioning (for example, Application administrator, Cloud Application administrator, Application Owner, or Global administrator). 
+* Single sign-on with Azure AD is completed.
+* A licensed or 30 days free trial account with directprint.io.
+
+## Step 1. Plan your provisioning deployment
+1. Learn about [how the provisioning service works](../app-provisioning/user-provisioning.md).
+1. Determine who will be in [scope for provisioning](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
+1. Determine what data to [map between Azure AD and directprint.io](../app-provisioning/customize-application-attributes.md). 
+
+## Step 2. Configure directprint.io to support provisioning with Azure AD
+
+1. log into your [directprint.io account](https://directprint.io/login/).
+1. Navigate to the Azure AD SSO and Provisioning screen.
+1. Save the Tenant URL and secret toke for future reference. You will need it in **Step 5**.
+
+  ![Provisioning Tenant URL and Provision secret](media/directprint/sso-provisioning-screen.png)
+
+## Step 3. Add directprint.io from the Azure AD application gallery
+
+Add directprint.io from the Azure AD application gallery to start managing provisioning to directprint.io. If you have previously setup directprint.io for SSO you can use the same application. However it is recommended that you create a separate app when testing out the integration initially. Learn more about adding an application from the gallery [here](../manage-apps/add-application-portal.md). 
+
+## Step 4. Define who will be in scope for provisioning 
+
+The Azure AD provisioning service allows you to scope who will be provisioned based on assignment to the application and or based on attributes of the user / group. If you choose to scope who will be provisioned to your app based on assignment, you can use the following [steps](../manage-apps/assign-user-or-group-access-portal.md) to assign users and groups to the application. If you choose to scope who will be provisioned based solely on attributes of the user or group, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). 
+
+* When assigning users and groups to directprint.io, you must select a role other than **Default Access**. Users with the Default Access role are excluded from provisioning and will be marked as not effectively entitled in the provisioning logs. If the only role available on the application is the default access role, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add additional roles. 
+
+* Start small. Test with a small set of users and groups before rolling out to everyone. When scope for provisioning is set to assigned users and groups, you can control this by assigning one or two users or groups to the app. When scope is set to all users and groups, you can specify an [attribute based scoping filter](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). 
+
+
+## Step 5. Configure automatic user provisioning to directprint.io 
+
+This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users and/or groups in directprint.io based on user and/or group assignments in Azure AD.
+
+### To configure automatic user provisioning for directprint.io in Azure AD:
+
+1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
+
+	![Enterprise applications blade](common/enterprise-applications.png)
+
+1. In the applications list, select **directprint.io**.
+
+	![The directprint.io link in the Applications list](common/all-applications.png)
+
+1. Select the **Provisioning** tab.
+
+	![Provisioning tab](common/provisioning.png)
+
+1. Set the **Provisioning Mode** to **Automatic**.
+
+	![Provisioning tab automatic](common/provisioning-automatic.png)
+
+1. Under the **Admin Credentials** section, input your directprint.io Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to directprint.io. If the connection fails, ensure your directprint.io account has Admin permissions and try again.
+
+ 	![Token](common/provisioning-testconnection-tenanturltoken.png)
+
+1. In the **Notification Email** field, enter the email address of a person or group who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
+
+	![Notification Email](common/provisioning-notification-email.png)
+
+1. Select **Save**.
+
+1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to directprint.io**.
+
+1. Review the user attributes that are synchronized from Azure AD to directprint.io in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in directprint.io for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you will need to ensure that the directprint.io API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
+
+   |Attribute|Type|Supported for filtering|
+   |---|---|---|
+   |userName|String|✓
+   |externalId|String|
+   |active|Boolean|
+
+1. Under the **Mappings** section, select **Synchronize Azure Active Directory Groups to directprint.io**.
+
+1. Review the group attributes that are synchronized from Azure AD to directprint.io in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the groups in directprint.io for update operations. Select the **Save** button to commit any changes.
+
+      |Attribute|Type|Supported for filtering|
+      |---|---|---|
+      |displayName|String|✓
+      |externalId|String|
+      |members|Reference|
+
+1. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
+
+1. To enable the Azure AD provisioning service for directprint.io, change the **Provisioning Status** to **On** in the **Settings** section.
+
+	![Provisioning Status Toggled On](common/provisioning-toggle-on.png)
+
+1. Define the users and/or groups that you would like to provision to directprint.io by choosing the desired values in **Scope** in the **Settings** section.
+
+	![Provisioning Scope](common/provisioning-scope.png)
+
+1. When you are ready to provision, click **Save**.
+
+	![Saving Provisioning Configuration](common/provisioning-configuration-save.png)
+
+This operation starts the initial synchronization cycle of all users and groups defined in **Scope** in the **Settings** section. The initial cycle takes longer to perform than subsequent cycles, which occur approximately every 40 minutes as long as the Azure AD provisioning service is running. 
+
+## Step 6. Monitor your deployment
+Once you've configured provisioning, use the following resources to monitor your deployment:
+
+* Use the [provisioning logs](../reports-monitoring/concept-provisioning-logs.md) to determine which users have been provisioned successfully or unsuccessfully
+* Check the [progress bar](../app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user.md) to see the status of the provisioning cycle and how close it is to completion
+* If the provisioning configuration seems to be in an unhealthy state, the application will go into quarantine. Learn more about quarantine states [here](../app-provisioning/application-provisioning-quarantine-status.md).  
+
+## More resources
+
+* [Managing user account provisioning for Enterprise Apps](../app-provisioning/configure-automatic-user-provisioning-portal.md)
+* [What is application access and single sign-on with Azure Active Directory?](../manage-apps/what-is-single-sign-on.md)
+
+## Next steps
+
+* [Learn how to review logs and get reports on provisioning activity](../app-provisioning/check-status-user-account-provisioning.md)

articles/active-directory/saas-apps/media/directprint/sso-provisioning-screen.png

@@ -2451,6 +2451,8 @@
         href: dynamic-signal-provisioning-tutorial.md
       - name: Dialpad
         href: dialpad-provisioning-tutorial.md
+      - name: directprint.io
+        href: directprint-io-provisioning-tutorial.md
       - name: Druva
         href: druva-provisioning-tutorial.md
       - name: Envoy