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

Author: Learn Build Service GitHub App

.openpublishing.redirection.active-directory.json

@@ -2731,7 +2731,7 @@
     },
     {
       "source_path_from_root": "/articles/active-directory/develop/howto-add-branding-in-azure-ad-apps.md",
-      "redirect_url": "/azure/active-directory/develop/howto-add-branding-in-apps.md",
+      "redirect_url": "/azure/active-directory/develop/howto-add-branding-in-apps",
       "redirect_document_id": false
     },
     {

includes/active-directory-develop-scenarios-call-apis-dotnet.md renamed to articles/active-directory/develop/includes/web-api/scenarios-call-apis-dotnet.md

@@ -24,8 +24,8 @@ The methods to acquire tokens return `AuthenticationResult`. For async methods,
 
 In MSAL.NET, `AuthenticationResult` exposes:
 
-- `AccessToken` for the web API to access resources. This parameter is a string, usually a Base-64-encoded JWT. The client should never look inside the access token. The format isn't guaranteed to remain stable, and it can be encrypted for the resource. Writing code that depends on access token content on the client is one of the biggest sources of errors and client logic breaks. For more information, see [Access tokens](../articles/active-directory/develop/access-tokens.md).
-- `IdToken` for the user. This parameter is an encoded JWT. For more information, see [ID tokens](../articles/active-directory/develop/id-tokens.md).
+- `AccessToken` for the web API to access resources. This parameter is a string, usually a Base-64-encoded JWT. The client should never look inside the access token. The format isn't guaranteed to remain stable, and it can be encrypted for the resource. Writing code that depends on access token content on the client is one of the biggest sources of errors and client logic breaks. For more information, see [Access tokens](../../access-tokens.md).
+- `IdToken` for the user. This parameter is an encoded JWT. For more information, see [ID tokens](../../id-tokens.md).
 - `ExpiresOn` tells the date and time when the token expires.
 - `TenantId` contains the tenant in which the user was found. For guest users in Azure Active Directory (Azure AD) B2B scenarios, the tenant ID is the guest tenant, not the unique tenant.
 When the token is delivered for a user, `AuthenticationResult` also contains information about this user. For confidential client flows where tokens are requested with no user for the application, this user information is null.

articles/active-directory/develop/scenario-daemon-call-api.md

@@ -124,7 +124,7 @@ data = requests.get(endpoint, headers=http_headers, stream=False).json()
 
 # [.NET low level](#tab/dotnet)
 
-[!INCLUDE [Call web API in .NET](../../../includes/active-directory-develop-scenarios-call-apis-dotnet.md)]
+[!INCLUDE [Call web API in .NET](./includes/web-api/scenarios-call-apis-dotnet.md)]
 
 ---
 

articles/active-directory/develop/scenario-desktop-call-api.md

@@ -24,7 +24,7 @@ Now that you have a token, you can call a protected web API.
 
 # [.NET](#tab/dotnet)
 
-[!INCLUDE [Call web API in .NET](../../../includes/active-directory-develop-scenarios-call-apis-dotnet.md)]
+[!INCLUDE [Call web API in .NET](./includes/web-api/scenarios-call-apis-dotnet.md)]
 
 # [Java](#tab/java)
 

articles/active-directory/develop/scenario-mobile-call-api.md

@@ -109,7 +109,7 @@ task.resume()
 
 ### Xamarin
 
-[!INCLUDE [Call web API in .NET](../../../includes/active-directory-develop-scenarios-call-apis-dotnet.md)]
+[!INCLUDE [Call web API in .NET](./includes/web-api/scenarios-call-apis-dotnet.md)]
 
 ## Make several API requests
 

articles/active-directory/roles/view-assignments.md

@@ -138,7 +138,7 @@ This section describes how to list role assignments with organization-wide scope
 Use the [List unifiedRoleAssignments](/graph/api/rbacapplication-list-roleassignments) API to get the role assignments for a specific role definition. The following example shows how to list the role assignments for a specific role definition with the ID `3671d40a-1aac-426c-a0c1-a3821ebd8218`.
 
 ```http
-GET https://graph.microsoft.com/v1.0/roleManagement/directory/roleAssignments&$filter=roleDefinitionId eq ‘<template-id-of-role-definition>’
+GET https://graph.microsoft.com/v1.0/roleManagement/directory/roleAssignments?$filter=roleDefinitionId eq ‘<template-id-of-role-definition>’
 ```
 
 Response

articles/active-directory/saas-apps/albert-provisioning-tutorial.md

@@ -0,0 +1,130 @@
+---
+title: 'Tutorial: Configure Albert for automatic user provisioning with Azure Active Directory'
+description: Learn how to automatically provision and de-provision user accounts from Azure AD to Albert.
+services: active-directory
+author: twimmers
+writer: twimmers
+manager: jeedes
+ms.assetid: b5672366-08ad-40ba-9cdf-7a24feff6c66
+ms.service: active-directory
+ms.subservice: saas-app-tutorial
+ms.workload: identity
+ms.topic: tutorial
+ms.date: 07/05/2023
+ms.author: thwimmer
+---
+
+# Tutorial: Configure Albert for automatic user provisioning
+
+This tutorial describes the steps you need to perform in both Albert and Azure Active Directory (Azure AD) to configure automatic user provisioning. When configured, Azure AD automatically provisions and de-provisions users to [Albert](https://www.albertinvent.com/) 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). 
+
+
+## Supported capabilities
+> [!div class="checklist"]
+> * Create users in Albert.
+> * Remove users in Albert when they do not require access anymore.
+> * Keep user attributes synchronized between Azure AD and Albert.
+> * [Single sign-on](../manage-apps/add-application-portal-setup-oidc-sso.md) to Albert (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).
+* A user account in Albert with Admin permissions.
+
+## 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 Albert](../app-provisioning/customize-application-attributes.md).
+
+## Step 2. Configure Albert to support provisioning with Azure AD
+Contact Albert support to configure Albert to support provisioning with Azure AD.
+
+## Step 3. Add Albert from the Azure AD application gallery
+
+Add Albert from the Azure AD application gallery to start managing provisioning to Albert. If you have previously setup Albert for SSO you can use the same application. However it's 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. 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 to the application. If you choose to scope who will be provisioned based solely on attributes of the user, you can use a scoping filter as described [here](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md). 
+
+* Start small. Test with a small set of users before rolling out to everyone. When scope for provisioning is set to assigned users, you can control this by assigning one or two users to the app. When scope is set to all users, you can specify an [attribute based scoping filter](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).
+
+* If you need more roles, you can [update the application manifest](../develop/howto-add-app-roles-in-azure-ad-apps.md) to add new roles.
+
+
+## Step 5. Configure automatic user provisioning to Albert 
+
+This section guides you through the steps to configure the Azure AD provisioning service to create, update, and disable users in TestApp based on user assignments in Azure AD.
+
+### To configure automatic user provisioning for Albert in Azure AD:
+
+1. Sign in to the [Azure portal](https://portal.azure.com). Select **Enterprise Applications**, then select **All applications**.
+
+	![Screenshot of Enterprise applications blade.](common/enterprise-applications.png)
+
+1. In the applications list, select **Albert**.
+
+	![Screenshot of the Albert link in the Applications list.](common/all-applications.png)
+
+1. Select the **Provisioning** tab.
+
+	![Screenshot of Provisioning tab.](common/provisioning.png)
+
+1. Set the **Provisioning Mode** to **Automatic**.
+
+	![Screenshot of Provisioning tab automatic.](common/provisioning-automatic.png)
+
+1. Under the **Admin Credentials** section, input your Albert Tenant URL and Secret Token. Click **Test Connection** to ensure Azure AD can connect to Albert. If the connection fails, ensure your Albert account has Admin permissions and try again.
+
+ 	![Screenshot of Token.](common/provisioning-testconnection-tenanturltoken.png)
+
+1. In the **Notification Email** field, enter the email address of a person who should receive the provisioning error notifications and select the **Send an email notification when a failure occurs** check box.
+
+	![Screenshot of Notification Email.](common/provisioning-notification-email.png)
+
+1. Select **Save**.
+
+1. Under the **Mappings** section, select **Synchronize Azure Active Directory Users to Albert**.
+
+1. Review the user attributes that are synchronized from Azure AD to Albert in the **Attribute-Mapping** section. The attributes selected as **Matching** properties are used to match the user accounts in Albert for update operations. If you choose to change the [matching target attribute](../app-provisioning/customize-application-attributes.md), you'll need to ensure that the Albert API supports filtering users based on that attribute. Select the **Save** button to commit any changes.
+
+   |Attribute|Type|Supported for filtering|Required by Albert|
+   |---|---|---|---|
+   |userName|String|✓|✓
+   |active|Boolean||✓
+   |externalId|String||✓
+
+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 Albert, change the **Provisioning Status** to **On** in the **Settings** section.
+
+	![Screenshot of Provisioning Status Toggled On.](common/provisioning-toggle-on.png)
+
+1. Define the users that you would like to provision to Albert by choosing the desired values in **Scope** in the **Settings** section.
+
+	![Screenshot of Provisioning Scope.](common/provisioning-scope.png)
+
+1. When you're ready to provision, click **Save**.
+
+	![Screenshot of Saving Provisioning Configuration.](common/provisioning-configuration-save.png)
+
+This operation starts the initial synchronization cycle of all users 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's to completion
+* If the provisioning configuration seems to be in an unhealthy state, the application goes 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)