Skip to content

Commit 1055d64

Browse files
committed
November 2022 added
1 parent e452045 commit 1055d64

File tree

1 file changed

+104
-0
lines changed

1 file changed

+104
-0
lines changed

articles/active-directory/fundamentals/whats-new-sovereign-clouds.md

Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,110 @@ Azure AD receives improvements on an ongoing basis. To stay up to date with the
2222
This page is updated monthly, so revisit it regularly.
2323

2424

25+
## November 2022
26+
27+
### Generally Availability - Windows Hello for Business, Cloud Kerberos Trust deployment
28+
29+
30+
31+
**Type:** New feature
32+
**Service category:** Authentications (Logins)
33+
**Product capability:** User Authentication
34+
35+
We're excited to announce the general availability of hybrid cloud Kerberos trust, a new Windows Hello for Business deployment model to enable a password-less sign-in experience. With this new model, we’ve made Windows Hello for Business much easier to deploy than the existing key trust and certificate trust deployment models by removing the need for maintaining complicated public key infrastructure (PKI), and Azure Active Directory (AD) Connect synchronization wait times. For more information, see: [Hybrid Cloud Kerberos Trust Deployment](/windows/security/identity-protection/hello-for-business/hello-hybrid-cloud-kerberos-trust).
36+
37+
---
38+
39+
### General Availability- Expression builder with Application Provisioning
40+
41+
**Type:** Changed feature
42+
**Service category:** Provisioning
43+
**Product capability:** Outbound to SaaS Applications
44+
45+
46+
Accidental deletion of users in your apps or in your on-premises directory could be disastrous. We’re excited to announce the general availability of the accidental deletions prevention capability. When a provisioning job would cause a spike in deletions, it will first pause and provide you visibility into the potential deletions. You can then accept or reject the deletions and have time to update the job’s scope if necessary. For more information, see [Understand how expression builder in Application Provisioning works](../app-provisioning/expression-builder.md).
47+
48+
49+
---
50+
51+
### General Availability - SSPR writeback is now available for disconnected forests using Azure AD Connect cloud sync
52+
53+
54+
55+
**Type:** New feature
56+
**Service category:** Azure AD Connect Cloud Sync
57+
**Product capability:** Identity Lifecycle Management
58+
59+
Azure AD Connect Cloud Sync Password writeback now provides customers the ability to synchronize Azure AD password changes made in the cloud to an on-premises directory in real time. This can be accomplished using the lightweight Azure AD cloud provisioning agent. For more information, see: [Tutorial: Enable cloud sync self-service password reset writeback to an on-premises environment](../authentication/tutorial-enable-cloud-sync-sspr-writeback.md).
60+
61+
---
62+
63+
### General Availability - Prevent accidental deletions
64+
65+
66+
67+
**Type:** New feature
68+
**Service category:** Provisioning
69+
**Product capability:** Outbound to SaaS Applications
70+
71+
72+
73+
Accidental deletion of users in any system could be disastrous. We’re excited to announce the general availability of the accidental deletions prevention capability as part of the Azure AD provisioning service. When the number of deletions to be processed in a single provisioning cycle spikes above a customer defined threshold, the Azure AD provisioning service will pause, provide you visibility into the potential deletions, and allow you to accept or reject the deletions. This functionality has historically been available for Azure AD Connect, and Azure AD Connect Cloud Sync. It's now available across the various provisioning flows, including both HR-driven provisioning and application provisioning.
74+
75+
For more information, see: [Enable accidental deletions prevention in the Azure AD provisioning service](../app-provisioning/accidental-deletions.md)
76+
77+
---
78+
79+
### General Availability - Create Group in Administrative Unit
80+
81+
**Type:** New feature
82+
**Service category:** RBAC
83+
**Product capability:** AuthZ/Access Delegation
84+
85+
86+
Groups Administrators and other roles scoped to an administrative unit can now create groups within the administrative unit. Previously, creating a new group in administrative unit required a two-step process to first create the group, then add the group to the administrative unit. The second step required a Privileged Role Administrator or Global Administrator. Now, groups can be directly created in an administrative unit by anyone with appropriate roles scoped to the administrative unit, and this no longer requires a higher privilege admin role. For more information, see: [Add users, groups, or devices to an administrative unit](../roles/admin-units-members-add.md).
87+
88+
---
89+
90+
### General Availability - Number Matching for Microsoft Authenticator notifications
91+
92+
93+
94+
**Type:** New feature
95+
**Service category:** Microsoft Authenticator App
96+
**Product capability:** User Authentication
97+
98+
To prevent accidental notification approvals, admins can now require users to enter the number displayed on the sign-in screen when approving an MFA notification in the Microsoft Authenticator app. We've also refreshed the Azure portal admin UX and Microsoft Graph APIs to make it easier for customers to manage Authenticator app feature roll-outs. As part of this update we have also added the highly requested ability for admins to exclude user groups from each feature.
99+
100+
The number matching feature greatly up-levels the security posture of the Microsoft Authenticator app and protects organizations from MFA fatigue attacks. We highly encourage our customers to adopt this feature applying the rollout controls we have built. Number Matching will begin to be enabled for all users of the Microsoft Authenticator app starting 27th of February 2023.
101+
102+
103+
For more information, see: [How to use number matching in multifactor authentication (MFA) notifications - Authentication methods policy](../authentication/how-to-mfa-number-match.md).
104+
105+
---
106+
107+
### General Availability - Additional context in Microsoft Authenticator notifications
108+
109+
110+
111+
**Type:** New feature
112+
**Service category:** Microsoft Authenticator App
113+
**Product capability:** User Authentication
114+
115+
Reduce accidental approvals by showing users additional context in Microsoft Authenticator app notifications. Customers can enhance notifications with the following:
116+
117+
- Application Context: This feature will show users which application they're signing into.
118+
- Geographic Location Context: This feature will show users their sign-in location based on the IP address of the device they're signing into.
119+
120+
The feature is available for both MFA and Password-less Phone Sign-in notifications and greatly increases the security posture of the Microsoft Authenticator app. We've also refreshed the Azure portal Admin UX and Microsoft Graph APIs to make it easier for customers to manage Authenticator app feature roll-outs. As part of this update, we've also added the highly requested ability for admins to exclude user groups from certain features.
121+
122+
We highly encourage our customers to adopt these critical security features to reduce accidental approvals of Authenticator notifications by end users.
123+
124+
125+
For more information, see: [How to use additional context in Microsoft Authenticator notifications - Authentication methods policy](../authentication/how-to-mfa-additional-context.md).
126+
127+
---
128+
25129

26130
## October 2022
27131

0 commit comments

Comments
 (0)