You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/whats-new.md
+33-6Lines changed: 33 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ This page is updated monthly, so revisit it regularly. If you're looking for ite
42
42
**Service category:** N/A
43
43
**Product capability:** User Authentication
44
44
45
-
For users who do not know or use a password, the Temporary Access Pass can now be used to recover Azure AD-joined PCs when the EnableWebSignIn policy is enabled on the device. For more information, see: [Authentication/EnableWebSignIn](/windows/client-management/mdm/policy-csp-authentication#authentication-enablewebsignin).
45
+
For users who don't know or use a password, the Temporary Access Pass can now be used to recover Azure AD-joined PCs when the EnableWebSignIn policy is enabled on the device. For more information, see: [Authentication/EnableWebSignIn](/windows/client-management/mdm/policy-csp-authentication#authentication-enablewebsignin).
46
46
47
47
48
48
---
@@ -77,7 +77,7 @@ For more information, see:
77
77
**Service category:** Microsoft Authenticator App
78
78
**Product capability:** User Authentication
79
79
80
-
Authenticator version 6.6.8 and higher on iOS will be FIPS 140 compliant for all Azure AD authentications using push multi-factor authentications (MFA), Password-less Phone Sign-In (PSI), and time-based one-time pass-codes (TOTP). No changes in configuration are required in the Authenticator app or Azure Portal to enable this capability. For more information, see: [FIPS 140 compliant for Azure AD authentication](../authentication/concept-authentication-authenticator-app.md#fips-140-compliant-for-azure-ad-authentication).
80
+
Authenticator version 6.6.8 and higher on iOS will be FIPS 140 compliant for all Azure AD authentications using push multi-factor authentications (MFA), Password-less Phone Sign-In (PSI), and time-based one-time pass-codes (TOTP). No changes in configuration are required in the Authenticator app or Azure portal to enable this capability. For more information, see: [FIPS 140 compliant for Azure AD authentication](../authentication/concept-authentication-authenticator-app.md#fips-140-compliant-for-azure-ad-authentication).
81
81
82
82
83
83
---
@@ -90,9 +90,9 @@ Authenticator version 6.6.8 and higher on iOS will be FIPS 140 compliant for all
90
90
**Service category:** Enterprise Apps
91
91
**Product capability:** 3rd Party Integration
92
92
93
-
In November 2022 we have added the following 22 new applications in our App gallery with Federation support
93
+
In November 2022, we've added the following 22 new applications in our App gallery with Federation support
You can also find the documentation of all the applications from here https://aka.ms/AppsTutorial,
98
98
@@ -140,7 +140,7 @@ Admins can now pause, and resume, the processing of individual dynamic groups in
140
140
**Service category:** Authentications (Logins)
141
141
**Product capability:** User Authentication
142
142
143
-
Update the Azure AD and Microsoft 365 login experience with new company branding capabilities. You can apply your company’s brand guidance to authentication experiences with pre-defined templates. For more information, see: [Configure your company branding](../fundamentals/customize-branding.md).
143
+
Update the Azure AD and Microsoft 365 sign in experience with new company branding capabilities. You can apply your company’s brand guidance to authentication experiences with pre-defined templates. For more information, see: [Configure your company branding](../fundamentals/customize-branding.md).
144
144
145
145
146
146
---
@@ -153,7 +153,7 @@ Update the Azure AD and Microsoft 365 login experience with new company branding
153
153
**Service category:** Directory Management
154
154
**Product capability:** Directory
155
155
156
-
Update the company branding functionality on the Azure AD/Microsoft 365 login experience to allow customizing Self Service Password Reset (SSPR) hyperlinks, footer hyperlinks and browser icon. For more information, see: [Configure your company branding](../fundamentals/customize-branding.md).
156
+
Update the company branding functionality on the Azure AD/Microsoft 365 sign in experience to allow customizing Self Service Password Reset (SSPR) hyperlinks, footer hyperlinks and browser icon. For more information, see: [Configure your company branding](../fundamentals/customize-branding.md).
157
157
158
158
159
159
---
@@ -171,6 +171,33 @@ Administrative Units now support soft deletion. Admins can now list, view proper
171
171
This functionality greatly enhances recoverability and resilience when using Administrative Units. Now, when an Administrative Unit is accidentally deleted, it can be restored quickly to the same state it was at time of deletion. This removes uncertainty around how things were configured, and makes restoration quick and easy. For more information, see: [Soft deletions](../fundamentals/recover-from-deletions.md#soft-deletions).
172
172
173
173
174
+
---
175
+
176
+
### Public Preview - IPv6 coming to Azure AD
177
+
178
+
179
+
180
+
**Type:** Plan for change
181
+
**Service category:** Identity Protection
182
+
**Product capability:** Platform
183
+
184
+
With the growing adoption and support of IPv6 across enterprise networks, service providers, and devices, many customers are wondering if their users can continue to access their services and applications from IPv6 clients and networks. Today, we’re excited to announce our plan to bring IPv6 support to Microsoft Azure Active Directory (Azure AD). This will allow customers to reach the Azure AD services over both IPv4 and IPv6 network protocols (dual stack).
185
+
For most customers, IPv4 won't completely disappear from their digital landscape, so we aren't planning to require IPv6 or to de-prioritize IPv4 in any Azure Active Directory features or services.
186
+
We'll begin introducing IPv6 support into Azure AD services in a phased approach, beginning March 31, 2023.
187
+
We have guidance below which is specifically for Azure AD customers who use IPv6 addresses and also use Named Locations in their Conditional Access policies.
188
+
189
+
Customers who use named locations to identify specific network boundaries in their organization need to:
190
+
1. Conduct an audit of existing named locations to anticipate potential impact.
191
+
1. Work with your network partner to identify egress IPv6 addresses in use in your environment.
192
+
1. Review and update existing named locations to include the identified IPv6 ranges.
193
+
194
+
Customers who use Conditional Access location based policies to restrict and secure access to their apps from specific networks need to:
195
+
1. Conduct an audit of existing Conditional Access policies to identify use of named locations as a condition to anticipate potential impact.
196
+
1. Review and update existing Conditional Access location based policies to ensure they continue to meet your organization’s security requirements.
197
+
198
+
We'll continue to share additional guidance on IPv6 enablement in Azure AD at this easy to remember link https://aka.ms/azureadipv6.
0 commit comments