Specify that Embedded IdP is Recommended

src/pages/selfhosted/identity-providers/authentik.mdx

@@ -86,7 +86,9 @@ After saving, NetBird displays the **Redirect URL**. Copy this URL and add it to
 
 ## Standalone Setup (Advanced)
 
-Use Authentik as your primary identity provider instead of the embedded IdP. This approach gives you full control over identity management but requires more configuration.
+Use Authentik as your primary identity provider instead of NetBird's embedded IdP. This option gives you full control over authentication and user management, is recommended for experienced Authentik administrators as it also requires additional setup and ongoing maintenance.
+
+For most deployments, the [embedded IdP](/selfhosted/identity-providers/embedded-idp) is the simpler choice — it's built into NetBird, fully integrated, and requires minimal configuration to get started. For this implementation, go back up to the [Connector Setup (Recommended)](#connector-setup-recommended) section above.
 
 <Note>
 If you prefer not to self-host an Identity and Access Management solution, you could use a managed alternative like [Auth0](/selfhosted/identity-providers/auth0).

src/pages/selfhosted/identity-providers/keycloak.mdx

@@ -71,7 +71,9 @@ Users who authenticate via Keycloak will appear in your NetBird Users list with
 
 ## Standalone Setup (Advanced)
 
-Use Keycloak as your primary identity provider instead of the embedded IdP. This approach gives you full control but requires more configuration.
+Use Keycloak as your primary identity provider instead of NetBird's embedded IdP. This option gives you full control over authentication and user management, is recommended for experienced Keycloak administrators as it also requires additional setup and ongoing maintenance.
+
+For most deployments, the [embedded IdP](/selfhosted/identity-providers/embedded-idp) is the simpler choice — it's built into NetBird, fully integrated, and requires minimal configuration to get started. For this implementation, go back up to the [Connector Setup (Recommended)](#connector-setup-recommended) section above.
 
 <Note>
 If you prefer not to self-host an Identity and Access Management solution, you could use a managed alternative like [Auth0](/selfhosted/identity-providers/auth0).

src/pages/selfhosted/identity-providers/managed/auth0.mdx

@@ -63,7 +63,9 @@ After saving, NetBird displays the **Redirect URL**. Copy this URL and add it to
 
 ## Standalone Setup (Advanced)
 
-Use Auth0 as your primary identity provider instead of the embedded IdP.
+Use Auth0 as your primary identity provider instead of NetBird's embedded IdP. This option gives you full control over authentication and user management, is recommended for experienced Auth0 administrators as it also requires additional setup and ongoing maintenance.
+
+For most deployments, the [embedded IdP](/selfhosted/identity-providers/embedded-idp) is the simpler choice — it's built into NetBird, fully integrated, and requires minimal configuration to get started. For this implementation, go back up to the [Connector Setup (Recommended)](#connector-setup-recommended) section above.
 
 <Note>
 If you prefer to have full control over authentication, consider self-hosted alternatives like [Keycloak](/selfhosted/identity-providers/keycloak).

src/pages/selfhosted/identity-providers/managed/google-workspace.mdx

@@ -84,7 +84,9 @@ Domain restrictions are configured in Google Cloud Console, not in NetBird.
 
 ## Standalone Setup (Advanced)
 
-Use Google Workspace as your primary identity provider instead of the embedded IdP. This enables full user management integration with Google Workspace.
+Use Google Workspace as your primary identity provider instead of NetBird's embedded IdP. This option gives you full control over authentication and user management, is recommended for experienced Google Workspace administrators as it also requires additional setup and ongoing maintenance.
+
+For most deployments, the [embedded IdP](/selfhosted/identity-providers/embedded-idp) is the simpler choice — it's built into NetBird, fully integrated, and requires minimal configuration to get started. For this implementation, go back up to the [Connector Setup (Recommended)](#connector-setup-recommended) section above.
 
 <Note>
 Beginning with NetBird version v0.23.6 and onwards, the Google Workspace IdP manager no longer requires the custom admin role called `User and Schema Management`. We now use a read-only role for user information.

src/pages/selfhosted/identity-providers/managed/jumpcloud.mdx

@@ -73,7 +73,9 @@ After saving, NetBird displays the **Redirect URL**. Copy this URL and add it to
 
 ## Standalone Setup (Advanced)
 
-Use JumpCloud as your primary identity provider instead of the embedded IdP.
+Use JumpCloud as your primary identity provider instead of NetBird's embedded IdP. This option gives you full control over authentication and user management, is recommended for experienced JumpCloud administrators as it also requires additional setup and ongoing maintenance.
+
+For most deployments, the [embedded IdP](/selfhosted/identity-providers/embedded-idp) is the simpler choice — it's built into NetBird, fully integrated, and requires minimal configuration to get started. For this implementation, go back up to the [Connector Setup (Recommended)](#connector-setup-recommended) section above.
 
 ### Prerequisites
 

src/pages/selfhosted/identity-providers/managed/microsoft-entra-id.mdx

@@ -89,7 +89,9 @@ After saving, NetBird displays the **Redirect URL**. Copy this URL and add it to
 
 ## Standalone Setup (Advanced)
 
-Use Microsoft Entra ID as your primary identity provider instead of the embedded IdP.
+Use Microsoft Entra ID as your primary identity provider instead of NetBird's embedded IdP. This option gives you full control over authentication and user management, is recommended for experienced Microsoft Entra ID administrators as it also requires additional setup and ongoing maintenance.
+
+For most deployments, the [embedded IdP](/selfhosted/identity-providers/embedded-idp) is the simpler choice — it's built into NetBird, fully integrated, and requires minimal configuration to get started. For this implementation, go back up to the [Connector Setup (Recommended)](#connector-setup-recommended) section above.
 
 <Note>
 If you prefer to have full control over authentication, consider self-hosted alternatives like [Keycloak](/selfhosted/identity-providers/keycloak).

src/pages/selfhosted/identity-providers/managed/okta.mdx

@@ -66,7 +66,9 @@ After saving, NetBird displays the **Redirect URL**. Copy this URL and add it to
 
 ## Standalone Setup (Advanced)
 
-Use Okta as your primary identity provider instead of the embedded IdP.
+Use Okta as your primary identity provider instead of NetBird's embedded IdP. This option gives you full control over authentication and user management, is recommended for experienced Okta administrators as it also requires additional setup and ongoing maintenance.
+
+For most deployments, the [embedded IdP](/selfhosted/identity-providers/embedded-idp) is the simpler choice — it's built into NetBird, fully integrated, and requires minimal configuration to get started. For this implementation, go back up to the [Connector Setup (Recommended)](#connector-setup-recommended) section above.
 
 <Note>
 If you prefer to have full control over authentication, consider self-hosted alternatives like [Keycloak](/selfhosted/identity-providers/keycloak).

src/pages/selfhosted/identity-providers/pocketid.mdx

@@ -67,7 +67,9 @@ After saving, NetBird displays the **Redirect URL**. Copy this URL and add it to
 
 ## Standalone Setup (Advanced)
 
-Use PocketID as your primary identity provider instead of the embedded IdP.
+Use PocketID as your primary identity provider instead of NetBird's embedded IdP. This option gives you full control over authentication and user management, is recommended for experienced PocketID administrators as it also requires additional setup and ongoing maintenance.
+
+For most deployments, the [embedded IdP](/selfhosted/identity-providers/embedded-idp) is the simpler choice — it's built into NetBird, fully integrated, and requires minimal configuration to get started. For this implementation, go back up to the [Connector Setup (Recommended)](#connector-setup-recommended) section above.
 
 ### Prerequisites
 

src/pages/selfhosted/identity-providers/zitadel.mdx

@@ -70,7 +70,9 @@ After saving, NetBird displays the **Redirect URL**. Copy this URL and add it to
 
 ## Standalone Setup (Advanced)
 
-Use Zitadel as your primary identity provider instead of the embedded IdP. This was the default approach in previous NetBird versions.
+Use Zitadel as your primary identity provider instead of NetBird's embedded IdP. This option gives you full control over authentication and user management, is recommended for experienced Zitadel administrators as it also requires additional setup and ongoing maintenance.
+
+For most deployments, the [embedded IdP](/selfhosted/identity-providers/embedded-idp) is the simpler choice — it's built into NetBird, fully integrated, and requires minimal configuration to get started. For this implementation, go back up to the [Connector Setup (Recommended)](#connector-setup-recommended) section above.
 
 <Note>
 If you prefer not to self-host, Zitadel offers a managed cloud option at [zitadel.com](https://zitadel.com/).