Skip to content

Commit bba8d03

Browse files
committed
Merge branch 'main' into release-mysql-single-server-deprecate
2 parents 8b6b793 + 646cddc commit bba8d03

File tree

111 files changed

+2422
-875
lines changed

Some content is hidden

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

111 files changed

+2422
-875
lines changed

articles/active-directory/enterprise-users/directory-delete-howto.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,8 @@ You can't delete a organization in Azure AD until it passes several checks. Thes
3030
* There can be no multifactor authentication providers linked to the organization.
3131
* There can be no subscriptions for any Microsoft Online Services such as Microsoft Azure, Microsoft 365, or Azure AD Premium associated with the organization. For example, if a default Azure AD tenant was created for you in Azure, you can't delete this organization if your Azure subscription still relies on it for authentication. You also can't delete a tenant if another user has associated an Azure subscription with it.
3232

33+
[!NOTE] Microsoft is aware that customers with certain tenant configurations may be unable to successfully delete their Azure AD organization. We are working to address this problem. In the meantime, if needed, you can contact Microsoft support for details about the issue.
34+
3335
## Delete the organization
3436

3537
1. Sign in to the [Azure AD admin center](https://aad.portal.azure.com) with an account that is the Global Administrator for your organization.

articles/active-directory/roles/permissions-reference.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,7 @@ This article lists the Azure AD built-in roles you can assign to allow managemen
8686
> | [Partner Tier1 Support](#partner-tier1-support) | Do not use - not intended for general use. | 4ba39ca4-527c-499a-b93d-d9b492c50246 |
8787
> | [Partner Tier2 Support](#partner-tier2-support) | Do not use - not intended for general use. | e00e864a-17c5-4a4b-9c06-f5b95a8d5bd8 |
8888
> | [Password Administrator](#password-administrator) | Can reset passwords for non-administrators and Password Administrators. | 966707d0-3269-4727-9be2-8c3a10f19b9d |
89+
> [Permissions Management Administrator](#permissions-management-administrator) | Can manage all aspects of Permissions Management. | af78dc32-cf4d-46f9-ba4e-4428526346b5 |
8990
> | [Power BI Administrator](#power-bi-administrator) | Can manage all aspects of the Power BI product. | a9ea8996-122f-4c74-9520-8edcd192826c |
9091
> | [Power Platform Administrator](#power-platform-administrator) | Can create and manage all aspects of Microsoft Dynamics 365, Power Apps and Power Automate. | 11648597-926c-4cf3-9c36-bcebb0ba8dcc |
9192
> | [Printer Administrator](#printer-administrator) | Can manage all aspects of printers and printer connectors. | 644ef478-e28f-4e28-b9dc-3fdde9aa0b1f |
@@ -1693,6 +1694,19 @@ Users with this role can't change the credentials or reset MFA for members and o
16931694
> | microsoft.directory/users/password/update | Reset passwords for all users |
16941695
> | microsoft.office365.webPortal/allEntities/standard/read | Read basic properties on all resources in the Microsoft 365 admin center |
16951696
1697+
## Permissions Management Administrator
1698+
1699+
Assign the Permissions Management Administrator role to users who need to do the following tasks:
1700+
1701+
- Manage all aspects of Entry Permissions Management, when the service is present
1702+
1703+
Learn more about Permissions Management roles and polices at [View information about roles/policies](../cloud-infrastructure-entitlement-management/how-to-view-role-policy.md).
1704+
1705+
> [!div class="mx-tableFixed"]
1706+
> | Actions | Description |
1707+
> | --- | --- |
1708+
> | microsoft.permissionsManagement/allEntities/allProperties/allTasks | Manage all aspects of Entra Permissions Management |
1709+
16961710
## Power BI Administrator
16971711

16981712
Users with this role have global permissions within Microsoft Power BI, when the service is present, as well as the ability to manage support tickets and monitor service health. More information at [Understanding the Power BI Administrator role](/power-bi/service-admin-role).

articles/active-directory/standards/memo-22-09-enterprise-wide-identity-management-system.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,18 +33,20 @@ Memorandum 22-09 requires agencies to develop a plan to consolidate their identi
3333

3434
## Why Azure Active Directory?
3535

36-
Azure Active Directory (Azure AD) provides the capabilities necessary to implement the recommendations from memorandum 22-09. It also provides broad identity controls that support Zero Trust initiatives. If your agency uses Microsoft Office 365, you already have an Azure AD back end to which you can consolidate.
36+
Azure Active Directory (Azure AD) provides the capabilities necessary to implement the recommendations from memorandum 22-09. It also provides broad identity controls that support Zero Trust initiatives. Today, If your agency uses Microsoft Office 365 or Azure, you already have Azure AD as an identity provider (IdP) and you can connect your applications and resources to Azure AD as your enterprise-wide identity system.
3737

3838
## Single sign-on requirements
3939

4040
The memo requires that users sign in once and then directly access applications. Microsoft's robust single sign-on (SSO) capabilities enable users to sign in once and then access cloud and other applications. For more information, see [Azure Active Directory single sign-on](../hybrid/how-to-connect-sso.md).
4141

4242
## Integration across agencies
4343

44-
[Azure AD B2B collaboration](../external-identities/what-is-b2b.md) helps you meet the requirement to facilitate integration among agencies. It does this by:
44+
[Azure AD B2B collaboration](../external-identities/what-is-b2b.md) helps you meet the requirement to facilitate integration/collaboration among agencies. Whether the users reside in different Microsoft tenant in the same cloud, [tenant on another microsoft cloud](../external-identities/b2b-government-national-clouds.md), or a [non Azure AD tenant (SAML/WS-Fed identity provider)](..//external-identities/direct-federation.md).
45+
46+
Azure AD cross-tenant access settings allow agencies to manage how they collaborate with other Azure AD organizations and other Microsoft Azure clouds. It does this by:
4547

4648
- Limiting what other Microsoft tenants your users can access.
47-
- Enabling you to allow access to users whom you don't have to manage in your own tenant, but whom you can subject to your multifactor authentication (MFA) and other access requirements.
49+
- Granular settings to control access for external users including enforcement of multifactor authentication (MFA) and device signal.
4850

4951
## Connecting applications
5052

@@ -119,6 +121,8 @@ Devices integrated with Azure AD can be either [hybrid joined devices](../device
119121

120122
* [Azure Linux virtual machines](../devices/howto-vm-sign-in-azure-ad-linux.md)
121123

124+
* [Azure Virtual Desktop](https://learn.microsoft.com/azure/architecture/example-scenario/wvd/azure-virtual-desktop-azure-active-directory-join)
125+
122126
* [Virtual desktop infrastructure](../devices/howto-device-identity-virtual-desktop-infrastructure.md)
123127

124128
## Next steps

0 commit comments

Comments
 (0)