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-sovereign-clouds.md
+85Lines changed: 85 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,91 @@ Azure AD receives improvements on an ongoing basis. To stay up to date with the
21
21
22
22
This page is updated monthly, so revisit it regularly.
23
23
24
+
## February 2023
25
+
26
+
### General Availability - Filter and transform group names in token claims configuration using regular expression
27
+
28
+
**Type:** New feature
29
+
**Service category:** Enterprise Apps
30
+
**Product capability:** SSO
31
+
32
+
Filter and transform group names in token claims configuration using regular expression. Many application configurations on ADFS and other IdPs rely on the ability to create authorization claims based on the content of Group Names using regular expression functions in the claim rules. Azure AD now has the capability to use a regular expression match and replace function to create claim content based on Group **onpremisesSAMAccount** names. This functionality will allow those applications to be moved to Azure AD for authentication using the same group management patterns. For more information, see: [Configure group claims for applications by using Azure Active Directory](../hybrid/how-to-connect-fed-group-claims.md).
33
+
34
+
---
35
+
36
+
### General Availability - Filter groups in tokens using a substring match
37
+
38
+
**Type:** New feature
39
+
**Service category:** Enterprise Apps
40
+
**Product capability:** SSO
41
+
42
+
Azure AD now has the capability to filter the groups included in the token using substring match on the display name or **onPremisesSAMAccountName** attributes of the group object. Only Groups the user is a member of will be included in the token.This was a blocker for some of our customers to migrate their apps from ADFS to Azure AD. This feature will unblock those challenges.
-[Configure group claims for applications by using Azure Active Directory](../hybrid/how-to-connect-fed-group-claims.md).
47
+
48
+
49
+
50
+
---
51
+
52
+
### General Availability - New SSO claims transformation features
53
+
54
+
**Type:** New feature
55
+
**Service category:** Enterprise Apps
56
+
**Product capability:** SSO
57
+
58
+
Azure AD now supports claims transformations on multi-valued attributes and can emit multi-valued claims. More functions to allow match and string operations on claims processing to enable apps to be migrated from other IdPs to Azure AD. This includes: Match on Empty(), NotEmpty(), Prefix(), Suffix(), and extract substring operators. For more information, see: [Claims mapping policy type](../develop/reference-claims-mapping-policy-type.md).
59
+
60
+
---
61
+
62
+
### General Availability - New Detection for Service Principal Behavior Anomalies
Post-authentication anomalous activity detection for workload identities. This detection focuses specifically on detection of post authenticated anomalous behavior performed by a workload identity (service principal). Post-authentication behavior will be assessed for anomalies based on an action and/or sequence of actions occurring for the account. Based on the scoring of anomalies identified, the offline detection may score the account as low, medium, or high risk. The risk allocation from the offline detection will be available within the Risky workload identities reporting blade. A new detection type identified as Anomalous service principal activity will appear in filter options. For more information, see: [Securing workload identities](../identity-protection/concept-workload-identity-risk.md).
69
+
70
+
---
71
+
72
+
### General Availability - Microsoft cloud settings for Azure AD B2B
73
+
74
+
**Type:** New feature
75
+
**Service category:** B2B
76
+
**Product capability:** B2B/B2C
77
+
78
+
Microsoft cloud settings let you collaborate with organizations from different Microsoft Azure clouds. With Microsoft cloud settings, you can establish mutual B2B collaboration between the following clouds:
79
+
80
+
- Microsoft Azure commercial and Microsoft Azure Government
81
+
- Microsoft Azure commercial and Microsoft Azure China 21Vianet
82
+
83
+
For more information about Microsoft cloud settings for B2B collaboration., see: [Microsoft cloud settings](../external-identities/cross-tenant-access-overview.md#microsoft-cloud-settings).
84
+
85
+
---
86
+
87
+
### Public Preview - Support for Directory Extensions using Azure AD cloud sync
88
+
89
+
**Type:** New feature
90
+
**Service category:** Provisioning
91
+
**Product capability:** Azure AD Connect Cloud Sync
92
+
93
+
Hybrid IT Admins now can sync both Active Directory and Azure AD Directory Extensions using Azure AD Cloud Sync. This new capability adds the ability to dynamically discover the schema for both Active Directory and Azure AD, allowing customers to map the needed attributes using Cloud Sync's attribute mapping experience.
94
+
95
+
For more information on how to enable this feature, see: [Cloud Sync directory extensions and custom attribute mapping](../cloud-sync/custom-attribute-mapping.md)
96
+
97
+
98
+
---
99
+
100
+
### General Availability - On-premises application provisioning
101
+
102
+
**Type:** Changed feature
103
+
**Service category:** Provisioning
104
+
**Product capability:** Outbound to On-premises Applications
105
+
106
+
Azure AD supports provisioning users into applications hosted on-premises or in a virtual machine, without having to open up any firewalls. If your application supports [SCIM](https://techcommunity.microsoft.com/t5/identity-standards-blog/provisioning-with-scim-getting-started/ba-p/880010), or you've built a SCIM gateway to connect to your legacy application, you can use the Azure AD Provisioning agent to [directly connect](../app-provisioning/on-premises-scim-provisioning.md) with your application and automate provisioning and deprovisioning. If you have legacy applications that don't support SCIM and rely on an [LDAP](../app-provisioning/on-premises-ldap-connector-configure.md) user store, or a [SQL](../app-provisioning/tutorial-ecma-sql-connector.md) database, Azure AD can support those as well.
0 commit comments