Skip to content

Commit 95269d1

Browse files
authored
Merge pull request #116471 from MicrosoftDocs/master
5/26 AM Publish
2 parents 1f25aa9 + befa3b1 commit 95269d1

File tree

53 files changed

+527
-506
lines changed

Some content is hidden

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

53 files changed

+527
-506
lines changed

.openpublishing.redirection.json

Lines changed: 107 additions & 102 deletions
Large diffs are not rendered by default.

articles/active-directory/authentication/howto-authentication-sms-signin.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: conceptual
9-
ms.date: 04/24/2020
9+
ms.date: 05/26/2020
1010

1111
ms.author: iainfou
1212
author: iainfoulds
@@ -36,9 +36,9 @@ To complete this article, you need the following resources and privileges:
3636
* An Azure Active Directory tenant associated with your subscription.
3737
* If needed, [create an Azure Active Directory tenant][create-azure-ad-tenant] or [associate an Azure subscription with your account][associate-azure-ad-tenant].
3838
* You need *global administrator* privileges in your Azure AD tenant to enable SMS-based authentication.
39-
* Each user that's enabled in the text message authentication method policy must be licensed, even if they don't use it. Each enabled user must have one of the following Azure AD, Office 365, or Microsoft 365 licenses:
39+
* Each user that's enabled in the text message authentication method policy must be licensed, even if they don't use it. Each enabled user must have one of the following Azure AD, EMS, Microsoft 365 licenses:
4040
* [Azure AD Premium P1 or P2][azuread-licensing]
41-
* [Microsoft 365 (M365) F1 or F3][m365-firstline-workers-licensing] or [Office 365 F1][o365-f1] or [F3][o365-f3]
41+
* [Microsoft 365 (M365) F1 or F3][m365-firstline-workers-licensing]
4242
* [Enterprise Mobility + Security (EMS) E3 or E5][ems-licensing] or [Microsoft 365 (M365) E3 or E5][m365-licensing]
4343

4444
## Limitations

articles/active-directory/develop/quickstart-v2-angular.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,6 @@ ms.author: janutter
1919

2020
# Quickstart: Sign in users and get an access token in an Angular single-page application
2121

22-
> [!IMPORTANT]
23-
> This feature is currently in preview. Previews are made available to you on the condition that you agree to the [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). Some aspects of this feature might change before general availability (GA).
24-
2522
In this quickstart, you use a code sample to learn how an Angular single-page application (SPA) can sign in users who have personal Microsoft accounts, work accounts, or school accounts. An Angular SPA can also get an access token to call the Microsoft Graph API or any web API.
2623

2724
## Prerequisites

articles/active-directory/hybrid/how-to-connect-sso-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Seamless SSO is a free feature and you don't need any paid editions of Azure AD
3232

3333
**Q: Is Seamless SSO available in the [Microsoft Azure Germany cloud](https://www.microsoft.de/cloud-deutschland) and the [Microsoft Azure Government cloud](https://azure.microsoft.com/features/gov/)?**
3434

35-
No. Seamless SSO is only available in the worldwide instance of Azure AD.
35+
Seamless SSO is available for the Azure Government cloud. For details, view [Hybrid Identity Considerations for Azure Government](https://docs.microsoft.com/azure/active-directory/hybrid/reference-connect-government-cloud).
3636

3737
**Q: What applications take advantage of `domain_hint` or `login_hint` parameter capability of Seamless SSO?**
3838

articles/active-directory/users-groups-roles/directory-assign-admin-roles.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -302,6 +302,21 @@ Users in this role can monitor all notifications in the Message Center, includin
302302

303303
Users in this role can monitor notifications and advisory health updates in [Office 365 Message center](https://support.office.com/article/Message-center-in-Office-365-38FB3333-BFCC-4340-A37B-DEDA509C2093) for their organization on configured services such as Exchange, Intune, and Microsoft Teams. Message Center Readers receive weekly email digests of posts, updates, and can share message center posts in Office 365. In Azure AD, users assigned to this role will only have read-only access on Azure AD services such as users and groups. This role has no access to view, create, or manage support tickets.
304304

305+
### [Modern Commerce Administrator](#modern-commerce-administrator-permissions)
306+
Do not use. This role is automatically assigned from Commerce, and is not intended or supported for any other use. See details below.
307+
308+
The Modern Commerce Administrator role gives certain users permission to access Microsoft 365 admin center and see the left navigation entries for **Home**, **Billing**, and **Support**. The content available in these areas is controlled by [commerce-specific roles](https://docs.microsoft.com/azure/cost-management-billing/manage/understand-mca-roles) assigned to users to manage products that they bought for themselves or your organization. This might include tasks like paying bills, or for access to billing accounts and billing profiles.
309+
310+
Users with the Modern Commerce Administrator role typically have administrative permissions in other Microsoft purchasing systems, but do not have Global administrator or Billing administrator roles used to access the admin center.
311+
312+
**When is the Modern Commerce Administrator role assigned?**
313+
* **Self-service purchase in Microsoft 365 admin center** – Self-service purchase gives users a chance to try out new products by buying or signing up for them on their own. These products are managed in the admin center. Users who make a self-service purchase are assigned a role in the commerce system, and the Modern Commerce Administrator role so they can manage their purchases in admin center. Admins can block self-service purchases (for Power BI, Power Apps, Power automate) through [PowerShell](https://docs.microsoft.com/microsoft-365/commerce/subscriptions/allowselfservicepurchase-powershell?view=o365-worldwide). For more information, see [Self-service purchase FAQ](https://docs.microsoft.com/microsoft-365/commerce/subscriptions/self-service-purchase-faq?view=o365-worldwide).
314+
* **Purchases from Microsoft commercial marketplace** – Similar to self-service purchase, when a user buys a product or service from Microsoft AppSource or Azure Marketplace, the Modern Commerce Administrator role is assigned if they don’t have the Global admin or Billing admin role. In some cases, users might be blocked from making these purchases. For more information, see [Microsoft commercial marketplace](https://docs.microsoft.com/azure/marketplace/marketplace-faq-publisher-guide#what-could-block-a-customer-from-completing-a-purchase).
315+
* **Proposals from Microsoft** – A proposal is a formal offer from Microsoft for your organization to buy Microsoft products and services. When the person who is accepting the proposal doesn’t have a Global admin or Billing admin role in Azure AD, they are assigned both a commerce-specific role to complete the proposal and the Modern Commerce Administrator role to access admin center. When they access the admin center they can only use features that are authorized by their commerce-specific role.
316+
* **Commerce-specific roles** – Some users are assigned commerce-specific roles. If a user isn't a Global or Billing admin, they get the Modern Commerce Administrator role so they can access the admin center.
317+
318+
If the Modern Commerce Administrator role is unassigned from a user, they lose access to Microsoft 365 admin center. If they were managing any products, either for themselves or for your organization, they won’t be able to manage them. This might include assigning licenses, changing payment methods, paying bills, or other tasks for managing subscriptions.
319+
305320
### [Network Administrator](#network-administrator-permissions)
306321

307322
Users in this role can review network perimeter architecture recommendations from Microsoft that are based on network telemetry from their user locations. Network performance for Office 365 relies on careful enterprise customer network perimeter architecture which is generally user location specific. This role allows for editing of discovered user locations and configuration of network parameters for those locations to facilitate improved telemetry measurements and design recommendations.
@@ -1313,6 +1328,23 @@ Can read messages and updates for their organization in Office 365 Message Cente
13131328
| microsoft.office365.webPortal/allEntities/basic/read | Read basic properties on all resources in microsoft.office365.webPortal. |
13141329
| microsoft.office365.messageCenter/messages/read | Read messages in microsoft.office365.messageCenter. |
13151330

1331+
### Modern Commerce Administrator permissions
1332+
Can manage commercial purchases for a company, department or team.
1333+
1334+
> [!NOTE]
1335+
> This role has additional permissions outside of Azure Active Directory. For more information, see role description above.
1336+
>
1337+
>
1338+
1339+
| **Actions** | **Description** |
1340+
| --- | --- |
1341+
| microsoft.commerce.billing/partners/read | Read partner property of O365 Billing. |
1342+
| microsoft.commerce.volumeLicenseServiceCenter/allEntities/allTasks | Manage all aspects of Volume Licensing Service Center. |
1343+
| microsoft.directory/organization/basic/update | Update basic properties on organization in Azure Active Directory. |
1344+
| microsoft.office365.supportTickets/allEntities/allTasks | Create and manage Office 365 support tickets. |
1345+
| microsoft.office365.webPortal/allEntities/basic/read | Read basic properties on all resources in microsoft.office365.webPortal. |
1346+
1347+
13161348
### Network Administrator permissions
13171349
Can manage network locations and review enterprise network design insights for Microsoft 365 Software as a Service applications.
13181350

@@ -1837,6 +1869,7 @@ License Administrator | License administrator | 4d6ac14f-3453-41d0-bef9-a3e0c569
18371869
Lync Service Administrator | Skype for Business administrator | 75941009-915a-4869-abe7-691bff18279e
18381870
Message Center Privacy Reader | Message center privacy reader | ac16e43d-7b2d-40e0-ac05-243ff356ab5b
18391871
Message Center Reader | Message center reader | 790c1fb9-7f7d-4f88-86a1-ef1f95c05c1b
1872+
Modern Commerce Administrator | Modern Commerce Administrator | d24aef57-1500-4070-84db-2666f29cf966
18401873
Network Administrator | Network administrator | d37c8bed-0711-4417-ba38-b4abe66ce4c2
18411874
Office Apps Administrator | Office apps administrator | 2b745bdf-0803-4d80-aa65-822c4493daac
18421875
Partner Tier1 Support | Not shown because it shouldn't be used | 4ba39ca4-527c-499a-b93d-d9b492c50246

articles/app-service/configure-authentication-provider-aad.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -152,7 +152,7 @@ You have now configured a daemon client application that can access your App Ser
152152
## <a name="related-content"> </a>Next steps
153153

154154
[!INCLUDE [app-service-mobile-related-content-get-started-users](../../includes/app-service-mobile-related-content-get-started-users.md)]
155-
155+
* [Tutorial: Authenticate and authorize users end-to-end in Azure App Service](app-service-web-tutorial-auth-aad.md)
156156
<!-- URLs. -->
157157

158158
[Azure portal]: https://portal.azure.com/

articles/azure-arc/kubernetes/connect-cluster.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -150,7 +150,7 @@ Helm release deployment succeeded
150150
List your connected clusters:
151151

152152
```console
153-
az connectedk8s list -g AzureArcTest
153+
az connectedk8s list -g AzureArcTest -o table
154154
```
155155

156156
**Output:**
@@ -215,4 +215,4 @@ To remove the agents in the cluster you need to run `az connectedk8s delete` or
215215
## Next steps
216216

217217
* [Use GitOps in a connected cluster](./use-gitops-connected-cluster.md)
218-
* [Use Azure Policy to govern cluster configuration](./use-azure-policy.md)
218+
* [Use Azure Policy to govern cluster configuration](./use-azure-policy.md)
39.4 KB
Loading
4.88 KB
Loading
13.1 KB
Loading

0 commit comments

Comments
 (0)