Update managed-identity.md

Author: PratimDasgupta

docs/sql-server/azure-arc/managed-identity.md

@@ -38,6 +38,7 @@ When using managed identity with SQL Server enabled by Azure Arc, consider the f
   - `Inbound connections` are logins and users connecting to SQL Server. Inbound connections can also be achieved by using [App registration](entra-authentication-setup-tutorial.md), starting in [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)].
   - `Outbound connections` are SQL Server connections to Azure resources, like backup to URL, or connecting to Azure Key Vault.
 - App Registration **can't** enable a SQL Server to make outbound connections. Outbound connections need a primary managed identity assigned to the SQL Server.
+- SQL Server 2025 and later recommends using managed identity based Entra setup, as detailed in this article. Alternatively, you can configure an [app registration for SQL Server 2025.](https://learn.microsoft.com/en-us/sql/relational-databases/security/authentication-access/microsoft-entra-authentication-sql-server-enable-without-arc)
 - \<There was some change here. Delete before publish\>
 
 ## Prerequisites