Skip to content

Commit 30cb6f2

Browse files
authored
Merge pull request #245148 from MicrosoftDocs/main
7/17/2023 AM Publish
2 parents 2d1e9ca + 48f948d commit 30cb6f2

File tree

98 files changed

+1027
-234
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

98 files changed

+1027
-234
lines changed

articles/active-directory/develop/access-tokens.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -111,6 +111,7 @@ Azure AD makes available a tenant-independent version of the document for multi-
111111
```
112112
113113
1. Applications that use Azure AD's tenant ID (`tid`) claim as a trust boundary instead of the standard issuer claim should ensure that the tenant-id claim is a GUID and that the issuer and tenant ID match.
114+
114115
Using tenant-independent metadata is more efficient for applications which accept tokens from many tenants.
115116
> [!NOTE]
116117
> With Azure AD tenant-independent metadata, claims should be interpreted within the tenant, just as under standard OpenID Connect, claims are interpreted within the issuer. That is, `{"sub":"ABC123","iss":"https://login.microsoftonline.com/{example-tenant-id}/v2.0","tid":"{example-tenant-id}"}` and `{"sub":"ABC123","iss":"https://login.microsoftonline.com/{another-tenand-id}/v2.0","tid":"{another-tenant-id}"}` describe different users, even though the `sub` is the same, because claims like `sub` are interpreted within the context of the issuer/tenant.

articles/active-directory/develop/includes/libraries/libraries-spa.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.author: henrymbugua
1010
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------- | :----------------------------------------------------------------------------------: | :---------------------------------------------------: | :-------------------------------------------------------------: | :----------------------------------------------------------: |
1111
| Angular | [MSAL Angular v2](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular)<sup>2</sup> | [msal-angular](https://www.npmjs.com/package/@azure/msal-angular) | [Tutorial](../../tutorial-v2-angular-auth-code.md) | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | GA |
1212
| Angular | [MSAL Angular](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/msal-angular-v1/lib/msal-angular)<sup>3</sup> | [msal-angular](https://www.npmjs.com/package/@azure/msal-angular) || ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | GA |
13-
| AngularJS | [MSAL AngularJS](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/maintenance/msal-angularjs)<sup>3</sup> | [msal-angularjs](https://www.npmjs.com/package/@azure/msal-angular) || ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | Public preview |
13+
| AngularJS | [MSAL AngularJS](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-angular)<sup>3</sup> | [msal-angularjs](https://www.npmjs.com/package/@azure/msal-angular) || ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | Public preview |
1414
| JavaScript | [MSAL.js v2](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-browser)<sup>2</sup> | [msal-browser](https://www.npmjs.com/package/@azure/msal-browser) | [Tutorial](../../tutorial-v2-javascript-auth-code.md) | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | GA |
1515
| JavaScript | [MSAL.js 1.0](/javascript/api/overview/msal-overview)<sup>3</sup> | [msal-core](https://www.npmjs.com/package/@azure/msal-core) || ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | GA |
1616
| React | [MSAL React](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-react)<sup>2</sup> | [msal-react](https://www.npmjs.com/package/@azure/msal-react) | [Tutorial](../../single-page-app-tutorial-01-register-app.md) | ![Library can request ID tokens for user sign-in.][y] | ![Library can request access tokens for protected web APIs.][y] | GA |

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ In this scenario, you've added the **Microsoft.Identity.Web.GraphServiceClient**
6868

6969
#### Option 2: Call a downstream web API with the helper class
7070

71-
In this scenario, you've added `.AddDownstreamWebApi()` in *Startup.cs* as specified in [Code configuration](scenario-web-api-call-api-app-configuration.md#option-2-call-a-downstream-web-api-other-than-microsoft-graph), and you can directly inject an `IDownstreamWebApi` service in your controller or page constructor and use it in the actions:
71+
In this scenario, you've added `.AddDownstreamApi()` in *Startup.cs* as specified in [Code configuration](scenario-web-api-call-api-app-configuration.md#option-2-call-a-downstream-web-api-other-than-microsoft-graph), and you can directly inject an `IDownstreamWebApi` service in your controller or page constructor and use it in the actions:
7272

7373
```csharp
7474
[Authorize]

articles/active-directory/develop/scenario-web-app-sign-user-sign-in.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -353,7 +353,7 @@ In Java, sign-out is handled by calling the Microsoft identity platform `logout`
353353

354354
# [Node.js](#tab/nodejs)
355355

356-
When the user selects the **Sign out** button, the app triggers the `/signout` route, which destroys the session and redirects the browser to Microsoft identity platform sign-out endpoint.
356+
When the user selects the **Sign out** button, the app triggers the `/auth/signout` route, which destroys the session and redirects the browser to Microsoft identity platform sign-out endpoint.
357357

358358
:::code language="js" source="~/ms-identity-node/App/auth/AuthProvider.js" range="157-175":::
359359

articles/active-directory/enterprise-users/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -142,7 +142,9 @@
142142
items:
143143
- name: Assign licenses to users
144144
href: ../fundamentals/license-users-groups.md?context=%2fazure%2factive-directory%2fenterprise-users%2fcontext%2fugr-context
145-
- name: Assign licenses to a group
145+
- name: Use Admin center to assign licenses to groups
146+
href: licensing-admin-center.md
147+
- name: Assign licenses to a group
146148
href: licensing-groups-assign.md
147149
- name: Resolve group license problems
148150
href: licensing-groups-resolve-problems.md
Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
title: Assign licenses to a group using the Microsoft 365 admin center
3+
description: How to assign licenses to groups using the Microsoft 365 admin center
4+
services: active-directory
5+
keywords: Azure AD licensing
6+
documentationcenter: ''
7+
author: barclayn
8+
manager: amycolannino
9+
10+
ms.service: active-directory
11+
ms.subservice: enterprise-users
12+
ms.topic: how-to
13+
ms.workload: identity
14+
ms.date: 07/17/2023
15+
ms.author: barclayn
16+
---
17+
18+
# Assign licenses to users by group membership using the Microsoft 365 admin center
19+
20+
This article shows you how to use the Microsoft 365 license center to assign licenses to a group.
21+
22+
> [!NOTE]
23+
> Some Microsoft services are not available in all locations. Before a license can be assigned to a user, the administrator has to specify the Usage location property on the user.
24+
>
25+
> For group license assignment, any users without a usage location specified inherit the location of the directory. If you have users in multiple locations, we recommend that you always set usage location as part of your user creation flow in Azure AD. For example, configure Azure AD Connect configuration to set usage location. This recommendation makes sure the result of license assignment is always correct and users do not receive services in locations that are not allowed.
26+
27+
## Assign a license
28+
29+
1. Sign in to the [Microsoft 365 admin center](https://admin.microsoft.com/) with a license administrator account. To manage licenses, the account must be a License Administrator, User Administrator, or Global Administrator.
30+
31+
![Screenshot of the Microsoft admin Center landing page](./media/licensing-admin-center/admin-center.png)
32+
33+
1. Browse to **Billing** > **Licenses** to open a page where you can see all licenses available in your organization.
34+
35+
![screenshot of portal section allowing user to select products to assign licenses](./media/licensing-admin-center/choose-licenses.png)
36+
37+
1. Under **Licenses**, select the license that you would like to assign.
38+
1. In the License details section, choose **Groups** at the top of the page.
39+
1. Choose **+ Assign licenses**
40+
1. From the **+ Assign licenses** page search for the group that you would like to use for license assignment.
41+
42+
![Screenshot of portal allowing users to choose the group to use for license assignment](./media/licensing-admin-center/assign-license-group.png)
43+
44+
>[!NOTE]
45+
>When assigning licenses to a group with service plans that have dependencies on other service plans, they must both be assigned together in the same group, otherwise the service plan with the dependency will be disabled.
46+
47+
1. To complete the assignment, on the **Assign license** page, click **Assign** at the bottom of the page.
48+
49+
![Screenshot of the portal section that allows you to choose assign after selecting the group](./media/licensing-admin-center/choose-assign.png)
50+
51+
When assign licenses to a group, Azure AD processes all existing members of that group. This process might take some time depending on the size of the group.
52+
53+
![Screenshot of message telling the administrator that they have assigned a license to a group](./media/licensing-admin-center/licenses-assignment-message.png)
54+
55+
## Verify that the initial assignment has finished
56+
57+
1. From the Admin Center, go to **Billing** > **Licenses**. Select the license that you assigned.
58+
59+
1. On the **License details** page, you can view the status of the license assignment operation. For example, in the image show below, you can see that **Contoso marketing** shows a status of **All licenses assigned** while **Contoso human resources** shows a status of **In progress**.
60+
61+
![Screenshot showing you the license assignment progress](./media/licensing-admin-center/progress.png)
62+
63+
[Read this section](licensing-group-advanced.md#use-audit-logs-to-monitor-group-based-licensing-activity) to learn more about how audit logs can be used to analyze changes made by group-based licensing.
64+
65+
66+
## Next steps
67+
68+
To learn more about the feature set for license assignment using groups, see the following articles:
69+
70+
- [What is group-based licensing in Azure Active Directory?](../fundamentals/active-directory-licensing-whatis-azure-portal.md?context=azure%2factive-directory%2fusers-groups-roles%2fcontext%2fugr-context)
71+
- [Identifying and resolving license problems for a group in Azure Active Directory](licensing-groups-resolve-problems.md)
152 KB
Loading
125 KB
Loading
27.2 KB
Loading
72.8 KB
Loading

0 commit comments

Comments
 (0)