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/manage-apps/configure-authentication-for-federated-users-portal.md
+23-21Lines changed: 23 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
8
8
ms.subservice: app-mgmt
9
9
ms.workload: infrastructure-services
10
10
ms.topic: how-to
11
-
ms.date: 01/02/2023
11
+
ms.date: 03/16/2023
12
12
ms.author: jomondi
13
13
ms.reviewer: ludwignick
14
14
ms.custom: seoapril2019, contperf-fy22q2
@@ -33,7 +33,8 @@ For federated users with cloud-enabled credentials, such as SMS sign-in or FIDO
33
33
To configure HRD policy for an application in Azure AD, you need:
34
34
35
35
- An Azure account with an active subscription. If you don't already have one, you can [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
36
-
- One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.
36
+
- One of the following roles: Global Administrator, or owner of the service principal.
37
+
37
38
::: zone pivot="powershell-hrd"
38
39
- The latest Azure AD PowerShell cmdlet preview.
39
40
::: zone-end
@@ -229,32 +230,33 @@ Set the HRD policy using Microsoft Graph. See [homeRealmDiscoveryPolicy](/graph/
229
230
230
231
From the Microsoft Graph explorer window:
231
232
232
-
1. Grant consent to the *Policy.ReadWrite.ApplicationConfiguration* permission.
233
-
1. Use the URL https://graph.microsoft.com/v1.0/policies/homeRealmDiscoveryPolicies
234
-
1. POST the new policy to this URL, or PATCH to https://graph.microsoft.com/v1.0/policies/homeRealmDiscoveryPolicies/{policyID} if overwriting an existing one.
235
-
1. POST or PATCH contents:
236
-
237
-
```json
238
-
{
239
-
"definition": [
240
-
"{\"HomeRealmDiscoveryPolicy\":
241
-
{\"AccelerateToFederatedDomain\":true,
242
-
\"PreferredDomain\":\"federated.example.edu\",
243
-
\"AlternateIdLogin\":{\"Enabled\":true}}}"
244
-
],
245
-
"displayName": "Home Realm Discovery auto acceleration",
246
-
"isOrganizationDefault": true
247
-
}
233
+
1. Sign in with one of the roles listed in the prerequisites section.
234
+
1. Grant consent to the `Policy.ReadWrite.ApplicationConfiguration` permission.
235
+
1. Use the [Home realm discovery policy](/graph/api/resources/homerealmdiscoverypolicy?view=graph-rest-1.0) to create a new policy.
236
+
1. POST the new policy, or PATCH to update an existing policy.
237
+
238
+
```http
239
+
PATCH /policies/homeRealmDiscoveryPolicies/{id}
240
+
{
241
+
"definition": [
242
+
"{\"HomeRealmDiscoveryPolicy\":
243
+
{\"AccelerateToFederatedDomain\":true,
244
+
\"PreferredDomain\":\"federated.example.edu\",
245
+
\"AlternateIdLogin\":{\"Enabled\":true}}}"
246
+
],
247
+
"displayName": "Home Realm Discovery auto acceleration",
248
+
"isOrganizationDefault": true
249
+
}
248
250
```
249
-
1. To see your new policy and get its ObjectID, run the following query:
251
+
1. To view your new policy, run the following query:
250
252
251
253
```http
252
-
GET https://graph.microsoft.com/v1.0/policies/homeRealmDiscoveryPolicies
254
+
GET /policies/homeRealmDiscoveryPolicies/{id}
253
255
```
254
256
1. To delete the HRD policy you created, run the query:
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/prevent-domain-hints-with-home-realm-discovery.md
+48-27Lines changed: 48 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
8
8
ms.subservice: app-mgmt
9
9
ms.workload: infrastructure-services
10
10
ms.topic: how-to
11
-
ms.date: 02/09/2022
11
+
ms.date: 03/16/2023
12
12
ms.author: jomondi
13
13
ms.reviewer: ludwignick
14
14
zone_pivot_groups: home-realm-discovery
@@ -51,7 +51,7 @@ Once a user has entered a username at the login page, they can use their managed
51
51
To disable auto-acceleration sign-in for an application in Azure AD, you need:
52
52
53
53
- An Azure account with an active subscription. If you don't already have one, you can [create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
54
-
- One of the following roles: Global Administrator, Cloud Application Administrator, Application Administrator, or owner of the service principal.
54
+
- One of the following roles: Global Administrator, or owner of the service principal.
55
55
::: zone pivot="powershell-hrd"
56
56
- The latest Azure AD PowerShell cmdlet preview.
57
57
::: zone-end
@@ -64,7 +64,9 @@ Admins of federated domains should set up this section of the HRD policy in a fo
2. Gather feedback from the test domain users. Collect details for applications that broke as a result of this change - they have a dependency on domain hint usage, and should be updated. For now, add them to the `RespectDomainHintForApps` section:
0 commit comments