Skip to content

Commit 7fc5945

Browse files
committed
article updates
1 parent 7472733 commit 7fc5945

File tree

2 files changed

+18
-18
lines changed

2 files changed

+18
-18
lines changed

articles/active-directory/fundamentals/whats-new-archive.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Archive for What's new in Azure Active Directory? | Microsoft Docs
3-
description: The What's new release notes in the Overview section of this content set contains 6 months of activity. After 6 months, the items are removed from the main article and put into this archive article.
3+
description: The What's new release notes in the Overview section of this content set contain 6 months of activity. After 6 months, the items are removed from the main article and put into this archive article.
44
services: active-directory
55
author: barclayn
66
manager: rkarlin
@@ -930,13 +930,13 @@ Users that have been assigned the User administrator role can longer create cata
930930

931931
---
932932

933-
### Windows Azure Active Directory connector is deprecated
933+
### Microsoft Azure Active Directory connector is deprecated
934934

935935
**Type:** Deprecated
936936
**Service category:** Microsoft Identity Manager
937937
**Product capability:** Identity Lifecycle Management
938938

939-
The Windows Azure AD Connector for FIM is at feature freeze and deprecated. The solution of using FIM and the Azure AD Connector has been replaced. Existing deployments should migrate to [Azure AD Connect](../hybrid/whatis-hybrid-identity.md), Azure AD Connect Sync, or the [Microsoft Graph Connector](/microsoft-identity-manager/microsoft-identity-manager-2016-connector-graph), as the internal interfaces used by the Azure AD Connector for FIM are being removed from Azure AD. [Learn more](/microsoft-identity-manager/microsoft-identity-manager-2016-deprecated-features).
939+
The Microsoft Azure Active Directory Connector for FIM is at feature freeze and deprecated. The solution of using FIM and the Azure AD Connector has been replaced. Existing deployments should migrate to [Azure AD Connect](../hybrid/whatis-hybrid-identity.md), Azure AD Connect Sync, or the [Microsoft Graph Connector](/microsoft-identity-manager/microsoft-identity-manager-2016-connector-graph), as the internal interfaces used by the Azure AD Connector for FIM are being removed from Azure AD. [Learn more](/microsoft-identity-manager/microsoft-identity-manager-2016-deprecated-features).
940940

941941
---
942942

@@ -2830,7 +2830,7 @@ It's recommended that customers use role template IDs in their PowerShell script
28302830

28312831
API connectors are now available for use with Azure Active Directory B2C. API connectors enable you to use web APIs to customize your sign-up user flows and integrate with external cloud systems. You can you can use API connectors to:
28322832

2833-
- Integrate with custom approval workflows
2833+
- Integrate with custom approval workflow
28342834
- Validate user input data
28352835
- Overwrite user attributes
28362836
- Run custom business logic
@@ -2978,7 +2978,7 @@ Azure AD Connect Cloud Provisioning public preview refresh features two major en
29782978

29792979
- On-demand Provisioning or Test User experience
29802980

2981-
Once you have setup your configuration, you might want to test to see if the user transformation is working as expected before applying it to all your users in scope. With on-demand provisioning, IT Admins can enter the Distinguished Name (DN) of an AD user and see if they're getting synced as expected. On-demand provisioning provides a great way to ensure that the attribute mappings you did previously work as expected. [Learn More](../cloud-sync/how-to-on-demand-provision.md)
2981+
Once you have set up your configuration, you might want to test to see if the user transformation is working as expected before applying it to all your users in scope. With on-demand provisioning, IT Admins can enter the Distinguished Name (DN) of an AD user and see if they're getting synced as expected. On-demand provisioning provides a great way to ensure that the attribute mappings you did previously work as expected. [Learn More](../cloud-sync/how-to-on-demand-provision.md)
29822982

29832983
---
29842984

@@ -3062,7 +3062,7 @@ For more information, please see [User management enhancements (preview) in Azur
30623062
**Service category:** Enterprise Apps
30633063
**Product capability:** SSO
30643064

3065-
You can add free text notes to Enterprise applications. You can add any relevant information that will help you manager applications under Enterprise applications. For more information, see [Quickstart: Configure properties for an application in your Azure Active Directory (Azure AD) tenant](../manage-apps/add-application-portal-configure.md).
3065+
You can add free text notes to Enterprise applications. You can add any relevant information that will help manager applications under Enterprise applications. For more information, see [Quickstart: Configure properties for an application in your Azure Active Directory (Azure AD) tenant](../manage-apps/add-application-portal-configure.md).
30663066

30673067
---
30683068

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

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -116,17 +116,17 @@ Pick a group of up to five members and provision them into your third-party appl
116116
---
117117

118118

119-
### General Availability – Protect against by-passing of cloud Azure MFA when federated with Azure AD
119+
### General Availability – Protect against by-passing of cloud Azure AD Multi-Factor Authentication when federated with Azure AD
120120

121121
**Type:** New feature
122122
**Service category:** MS Graph
123123
**Product capability:** Identity Security & Protection
124124

125125

126-
We're delighted to announce a new security protection that prevents bypassing of cloud Azure MFA when federated with Azure AD. When enabled for a federated domain in your Azure AD tenant, it ensures that a compromised federated account can't bypass Azure MFA by imitating that a multi factor authentication has already been performed by the identity provider. The protection can be enabled via new security setting, [federatedIdpMfaBehavior](/graph/api/resources/internaldomainfederation?view=graph-rest-beta#federatedidpmfabehavior-values).
126+
We're delighted to announce a new security protection that prevents bypassing of cloud Azure AD Multi-Factor Authentication when federated with Azure AD. When enabled for a federated domain in your Azure AD tenant, it ensures that a compromised federated account can't bypass Azure AD Multi-Factor Authentication by imitating that a multi factor authentication has already been performed by the identity provider. The protection can be enabled via new security setting, [federatedIdpMfaBehavior](/graph/api/resources/internaldomainfederation?view=graph-rest-beta#federatedidpmfabehavior-values).
127127

128128

129-
We highly recommend enabling this new protection when using Azure MFA as your multi factor authentication for your federated users. To learn more about the protection and how to enable it, visit [Enable protection to prevent by-passing of cloud Azure MFA when federated with Azure AD](/windows-server/identity/ad-fs/deployment/best-practices-securing-ad-fs#enable-protection-to-prevent-by-passing-of-cloud-azure-ad-multi-factor-authentication-when-federated-with-azure-ad).
129+
We highly recommend enabling this new protection when using Azure AD Multi-Factor Authentication as your multi factor authentication for your federated users. To learn more about the protection and how to enable it, visit [Enable protection to prevent by-passing of cloud Azure AD Multi-Factor Authentication when federated with Azure AD](/windows-server/identity/ad-fs/deployment/best-practices-securing-ad-fs#enable-protection-to-prevent-by-passing-of-cloud-azure-ad-multi-factor-authentication-when-federated-with-azure-ad).
130130

131131

132132
---
@@ -156,7 +156,7 @@ For more information about how to better secure your organization by using autom
156156
**Product capability:** Platform
157157

158158

159-
Azure Service Health supports service outage notifications to Tenant Admins for Azure Active Directory issues. These outages will also appear on the Azure AD Admin Portal Overview page with appropriate links to Azure Service Health. Outage events will be able to be seen by built-in Tenant Administrator Roles. We'll continue to send outage notifications to subscriptions within a tenant for a period of transition. More information is available at: [What are Service Health notifications in Azure Active Directory?](../reports-monitoring/overview-service-health-notifications.md).
159+
Azure Service Health supports service outage notifications to Tenant Admins for Azure Active Directory issues. These outages will also appear on the Azure AD Admin Portal Overview page with appropriate links to Azure Service Health. Outage events will be able to be seen by built-in Tenant Administrator Roles. We'll continue to send outage notifications to subscriptions within a tenant for transition. More information is available at: [What are Service Health notifications in Azure Active Directory?](../reports-monitoring/overview-service-health-notifications.md).
160160

161161

162162

@@ -174,7 +174,7 @@ Azure Service Health supports service outage notifications to Tenant Admins for
174174
End users can now enable passwordless phone sign-in for multiple accounts in the Authenticator App on any supported iOS device. Consultants, students, and others with multiple accounts in Azure AD can add each account to Microsoft Authenticator and use passwordless phone sign-in for all of them from the same iOS device. The Azure AD accounts can be in either the same, or different, tenants. Guest accounts aren't supported for multiple account sign-ins from one device.
175175

176176

177-
Please note that, end users are encouraged to enable the optional telemetry setting in the Authenticator App, if not done so already. For more information, see: [Enable passwordless sign-in with Microsoft Authenticator](../authentication/howto-authentication-passwordless-phone.md)
177+
Note that end users are encouraged to enable the optional telemetry setting in the Authenticator App, if not done so already. For more information, see: [Enable passwordless sign-in with Microsoft Authenticator](../authentication/howto-authentication-passwordless-phone.md)
178178

179179

180180

@@ -255,7 +255,7 @@ Accidental deletion of users in your apps or in your on-premises directory could
255255
**Product capability:** End User Experiences
256256

257257

258-
An improved app discovery view for My Apps is in public preview. The preview shows users more apps in the same space and allows them to scroll between collections. It does not currently support drag-and-drop and list view. Users can opt into the preview by selecting Try the preview and opt out by selecting Return to previous view. To learn more about My Apps, see [My Apps portal overview](../manage-apps/myapps-overview.md).
258+
An improved app discovery view for My Apps is in public preview. The preview shows users more apps in the same space and allows them to scroll between collections. It doesn't currently support drag-and-drop and list view. Users can opt into the preview by selecting Try the preview and opt out by selecting Return to previous view. To learn more about My Apps, see [My Apps portal overview](../manage-apps/myapps-overview.md).
259259

260260

261261

@@ -306,7 +306,7 @@ For more information, see: [Customize app SAML token claims - Microsoft identity
306306

307307

308308

309-
### Public Preview - ADFS to Azure AD: Customize attrname-format​
309+
### Public Preview - ADFS to Azure Active Directory: Customize attrname-format​
310310

311311
**Type:** Changed feature
312312
**Service category:** Enterprise Apps
@@ -376,7 +376,7 @@ Temporary Access Pass (TAP) is now generally available. TAP can be used to secur
376376

377377

378378

379-
Create "nested" groups with Azure AD Dynamic Groups! This feature enables you to build dynamic Azure AD Security Groups and M365 groups based on other groups! For example, you can now create Dynamic-Group-A with members of Group-X and Group-Y. For more information, see: [Steps to create a memberOf dynamic group](../enterprise-users/groups-dynamic-rule-member-of.md#steps-to-create-a-memberof-dynamic-group).
379+
Create "nested" groups with Azure AD Dynamic Groups! This feature enables you to build dynamic Azure AD Security Groups and Microsoft 365 groups based on other groups! For example, you can now create Dynamic-Group-A with members of Group-X and Group-Y. For more information, see: [Steps to create a memberOf dynamic group](../enterprise-users/groups-dynamic-rule-member-of.md#steps-to-create-a-memberof-dynamic-group).
380380

381381

382382
---
@@ -544,14 +544,14 @@ For more information about how to better secure your organization by using autom
544544
---
545545

546546

547-
### Public Preview: Confirm safe and compromised in signIns API beta
547+
### Public Preview: Confirm safe and compromised in sign-ins API beta
548548

549549
**Type:** New feature
550550
**Service category:** Identity Protection
551551
**Product capability:** Identity Security & Protection
552552

553553

554-
The signIns Microsoft Graph API now supports confirming safe and compromised on risky sign-ins. This public preview functionality is available at the beta endpoint. For more information, please check out the Microsoft Graph documentation: [signIn: confirmSafe - Microsoft Graph beta | Microsoft Docs](/graph/api/signin-confirmsafe?view=graph-rest-beta&preserve-view=true)
554+
The sign-ins Microsoft Graph API now supports confirming safe and compromised on risky sign-ins. This public preview functionality is available at the beta endpoint. For more information, please check out the Microsoft Graph documentation: [signIn: confirmSafe - Microsoft Graph beta | Microsoft Docs](/graph/api/signin-confirmsafe?view=graph-rest-beta&preserve-view=true)
555555

556556

557557
---
@@ -686,7 +686,7 @@ With a recent improvement, Smart Lockout now synchronizes the lockout state acro
686686
---
687687

688688

689-
### Public Preview - Integration of Microsoft 365 App Certification details into AAD UX and Consent Experiences
689+
### Public Preview - Integration of Microsoft 365 App Certification details into Azure Active Directory UX and Consent Experiences
690690

691691
**Type:** New feature
692692
**Service category:** User Access Management
@@ -1050,7 +1050,7 @@ For more information about how to better secure your organization by using autom
10501050
**Product capability:** Privileged Identity Management
10511051

10521052

1053-
We have improved the Privileged Identity management (PIM) time to role activation for SharePoint Online. Now, when activating a role in PIM for SharePoint Online, you should be able to use your permissions right away in SharePoint Online. This change will roll out in stages, so you might not yet see these improvements in your organization. [Learn more](../privileged-identity-management/pim-how-to-activate-role.md)
1053+
We've improved the Privileged Identity management (PIM) time to role activation for SharePoint Online. Now, when activating a role in PIM for SharePoint Online, you should be able to use your permissions right away in SharePoint Online. This change will roll out in stages, so you might not yet see these improvements in your organization. [Learn more](../privileged-identity-management/pim-how-to-activate-role.md)
10541054

10551055

10561056
---

0 commit comments

Comments
 (0)