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/f5-big-ip-kerberos-easy-button.md
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Integrating a BIG-IP with Azure Active Directory (Azure AD) provides many benefi
23
23
* Improved governance: See, [Zero Trust framework to enable remote work](https://www.microsoft.com/security/blog/2020/04/02/announcing-microsoft-zero-trust-assessment-tool/) and learn more about Azure AD pre-authentication.
24
24
* Enforce organizational policies. See [What is Conditional Access?](../conditional-access/overview.md).
25
25
* Full SSO between Azure AD and BIG-IP published services
26
-
* Manage identities and access from a single control plane, the [Azure portal](https://portal.azure.com)
26
+
* Manage identities and access from a single control plane, the [Microsoft Entra admin center](https://entra.microsoft.com).
27
27
28
28
To learn more about benefits, see the article on [F5 BIG-IP and Azure AD integration](./f5-integration.md).
29
29
@@ -71,7 +71,7 @@ Prior BIG-IP experience isn't necessary, but you need:
71
71
* F5 BIG-IP APM add-on license on a BIG-IP F5 BIG-IP® Local Traffic Manager™ (LTM)
* User identities [synchronized](../hybrid/connect/how-to-connect-sync-whatis.md) from an on-premises directory to Azure AD, or created in Azure AD and flowed back to your on-premises directory
74
-
*An account with Azure AD Application Admin [permissions](/azure/active-directory/users-groups-roles/directory-assign-admin-roles#application-administrator)
74
+
*One of the following roles: Global Administrator, Cloud Application Administrator, or Application Administrator.
75
75
* An [SSL Web certificate](./f5-bigip-deployment-guide.md) for publishing services over HTTPS, or use the default BIG-IP certificates while testing
76
76
* A Kerberos application, or go to active-directory-wp.com to learn to configure [SSO with IIS on Windows](https://active-directory-wp.com/docs/Networking/Single_Sign_On/SSO_with_IIS_on_Windows.html).
77
77
@@ -88,13 +88,12 @@ This tutorial covers the latest Guided Configuration 16.1 with an Easy Button te
88
88
89
89
Before a client or service can access Microsoft Graph, it must be trusted by the [Microsoft identity platform.](../develop/quickstart-register-app.md). This action creates a tenant app registration to authorize Easy Button access to Graph. Through these permissions, the BIG-IP pushes the configurations to establish a trust between a SAML SP instance for published application, and Azure AD as the SAML IdP.
90
90
91
-
1. Sign in to the [Azure portal](https://portal.azure.com) using an account with Application Admin permissions.
92
-
2. From the left navigation pane, select the **Azure Active Directory** service.
93
-
3. Under Manage, select **App registrations > New registration**.
94
-
4. Enter a display name for your application. For example, F5 BIG-IP Easy Button.
95
-
5. Specify who can use the application > **Accounts in this organizational directory only**.
96
-
6. Select **Register**.
97
-
7. Navigate to **API permissions** and authorize the following Microsoft Graph **Application permissions**:
91
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
92
+
2. Browse to **Identity** > **Applications** > **App registrations > New registration**.
93
+
3. Enter a display name for your application. For example, F5 BIG-IP Easy Button.
94
+
4. Specify who can use the application > **Accounts in this organizational directory only**.
95
+
5. Select **Register**.
96
+
6. Navigate to **API permissions** and authorize the following Microsoft Graph **Application permissions**:
0 commit comments