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-b2c/partner-gallery.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ Microsoft partners with the following ISVs to provide secure hybrid access to on
76
76
77
77
| ISV partner | Description and integration walkthroughs |
78
78
|:-------------------------|:--------------|
79
-
||[Akamai](./partner-akamai-secure-hybrid-access.md)is a Zero Trust Network Access (ZTNA) solution that enables secure remote access to modern and legacy applications that reside in private datacenters. |
79
+
||[Akamai](./partner-akamai-secure-hybrid-access.md)provides a Zero Trust Network Access (ZTNA) solution that enables secure remote access to modern and legacy applications that reside in private datacenters. |
80
80
||[Datawiza](./partner-datawiza.md) enables SSO and granular access control for your applications and extends Azure AD B2C to protect on-premises legacy applications. |
81
81
||[F5](./partner-f5.md) enables legacy applications to securely expose to the internet through BIG-IP security combined with Azure AD B2C pre-authentication, Conditional Access (CA) and SSO. |
82
82
||[Ping Identity](./partner-ping-identity.md) enables secure hybrid access to on-premises legacy applications across multiple clouds. |
Copy file name to clipboardExpand all lines: articles/active-directory/app-provisioning/on-premises-ecma-troubleshoot.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ manager: amycolannino
7
7
ms.service: active-directory
8
8
ms.workload: identity
9
9
ms.topic: overview
10
-
ms.date: 11/12/2022
10
+
ms.date: 11/29/2022
11
11
ms.subservice: hybrid
12
12
ms.author: billmath
13
13
ms.collection: M365-identity-device-management
@@ -44,7 +44,15 @@ After you configure the provisioning agent and ECMA host, it's time to test conn
44
44
7. Ensure that you're using a valid certificate that has not expired. Go to the **Settings** tab of the ECMA host to view the certificate expiration date. If the certificate has expired, click `Generate certificate` to generate a new certificate.
45
45
8. Restart the provisioning agent by going to the taskbar on your VM by searching for the Microsoft Azure AD Connect provisioning agent. Right-click **Stop**, and then select **Start**.
46
46
1. If you continue to see `The ECMA host is currently importing data from the target application` even after restarting the ECMA Connector Host and the provisioning agent, and waiting for the initial import to complete, then you may need to cancel and start over configuring provisioning to the application in the Azure portal.
47
-
1. When you provide the tenant URL in the Azure portal, ensure that it follows the following pattern. You can replace `localhost` with your host name, but it isn't required. Replace `connectorName` with the name of the connector you specified in the ECMA host. The error message 'invalid resource' generally indicates that the URL does not follow the expected format.
47
+
1. When configuring the ECMA host, ensure that you provide a certificate with a subject that matches the hostname of your windows server. The certificate that is generated by the ECMA host will do this for you automatically, but should only be used for testing purposes.
Details: We received this unexpected response from your application: Received response from Web resource. Resource: https://localhost/Users?filter=PLACEHOLDER+eq+"8646d011-1693-4cd3-9ee6-0d7482ca2219" Operation: GET Response Status Code: InternalServerError Response Headers: Response Content: An error occurred while sending the request. Please check the service and try again.
53
+
```
54
+
55
+
1. When you provide the tenant URL in the Azure portal, ensure that it follows the following pattern. You can replace `localhost` with your host name, but it isn't required. Replace `connectorName` with the name of the connector you specified in the ECMA host. The error message 'invalid resource' generally indicates that the URL does not follow the expected format.
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/whats-new.md
+168Lines changed: 168 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,174 @@ Azure AD receives improvements on an ongoing basis. To stay up to date with the
32
32
This page is updated monthly, so revisit it regularly. If you're looking for items older than six months, you can find them in [Archive for What's new in Azure Active Directory](whats-new-archive.md).
33
33
34
34
35
+
## November 2022
36
+
37
+
### General Availability - use Web Sign-in on Windows for password-less recovery with Temporary Access Pass
38
+
39
+
40
+
41
+
**Type:** Changed feature
42
+
**Service category:** N/A
43
+
**Product capability:** User Authentication
44
+
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
+
47
+
48
+
---
49
+
50
+
### Public Preview - Workload identity Federation for Managed Identities
51
+
52
+
53
+
54
+
**Type:** New feature
55
+
**Service category:** Managed identities for Azure resources
56
+
**Product capability:** Developer Experience
57
+
58
+
Developers can now use managed identities for their software workloads running anywhere, and for accessing Azure resources, without needing secrets. Key scenarios include:
59
+
60
+
- Accessing Azure resources from Kubernetes pods running on-premises or in any cloud.
61
+
- GitHub workflows to deploy to Azure, no secrets necessary.
62
+
- Accessing Azure resources from other cloud platforms that support OIDC, such as Google Cloud.
63
+
64
+
For more information, see:
65
+
-[Configure a user-assigned managed identity to trust an external identity provider (preview)](../develop/workload-identity-federation-create-trust-user-assigned-managed-identity.md)
-[Use an Azure AD workload identity (preview) on Azure Kubernetes Service (AKS)](/azure/aks/workload-identity-overview)
68
+
69
+
70
+
---
71
+
72
+
### General Availability - Authenticator on iOS is FIPS 140 compliant
73
+
74
+
75
+
76
+
**Type:** New feature
77
+
**Service category:** Microsoft Authenticator App
78
+
**Product capability:** User Authentication
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).
81
+
82
+
83
+
---
84
+
85
+
### General Availability - New Federated Apps available in Azure AD Application gallery - November 2022
86
+
87
+
88
+
89
+
**Type:** New feature
90
+
**Service category:** Enterprise Apps
91
+
**Product capability:** 3rd Party Integration
92
+
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
+
99
+
For listing your application in the Azure AD app gallery, please read the details here https://aka.ms/AzureADAppRequest
100
+
101
+
102
+
---
103
+
104
+
### General Availability - New provisioning connectors in the Azure AD Application Gallery - November 2022
105
+
106
+
107
+
108
+
**Type:** New feature
109
+
**Service category:** App Provisioning
110
+
**Product capability:** 3rd Party Integration
111
+
112
+
We've added the following new applications in our App gallery with Provisioning support. You can now automate creating, updating, and deleting of user accounts for these newly integrated apps:
For more information about how to better secure your organization by using automated user account provisioning, see: [Automate user provisioning to SaaS applications with Azure AD](../app-provisioning/user-provisioning.md).
118
+
119
+
120
+
---
121
+
122
+
### Public Preview - Dynamic Group Pause Functionality
123
+
124
+
125
+
126
+
**Type:** New feature
127
+
**Service category:** Group Management
128
+
**Product capability:** Directory
129
+
130
+
Admins can now pause, and resume, the processing of individual dynamic groups in the Entra Admin Center. For more information, see: [Create or update a dynamic group in Azure Active Directory](../enterprise-users/groups-create-rule.md).
131
+
132
+
133
+
---
134
+
135
+
### Public Preview - Enabling extended customization capabilities for sign-in and sign-up pages in Company Branding capabilities.
136
+
137
+
138
+
139
+
**Type:** New feature
140
+
**Service category:** Authentications (Logins)
141
+
**Product capability:** User Authentication
142
+
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
+
145
+
146
+
---
147
+
148
+
### Public Preview - Enabling customization capabilities for the Self-Service Password Reset (SSPR) hyperlinks, footer hyperlinks and browser icons in Company Branding.
149
+
150
+
151
+
152
+
**Type:** New feature
153
+
**Service category:** Directory Management
154
+
**Product capability:** Directory
155
+
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
+
158
+
159
+
---
160
+
161
+
### General Availability - Soft Delete for Administrative Units
162
+
163
+
164
+
165
+
**Type:** New feature
166
+
**Service category:** B2B
167
+
**Product capability:** B2B/B2C
168
+
169
+
Administrative Units now support soft deletion. Admins can now list, view properties of, perform ad hoc hard delete, or restore deleted Administrative Units using Microsoft Graph. This functionality restores all configuration for the Administrative Unit when restored from soft delete including: memberships, admin roles, processing rules, and processing rules state.
170
+
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
+
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.
199
+
200
+
201
+
---
202
+
35
203
## October 2022
36
204
37
205
### General Availability - Upgrade Azure AD Provisioning agent to the latest version (version number: 1.1.977.0)
0 commit comments