Microsoft Entra Connect

๐Ÿ”’Secure Bits๐Ÿ’ก
Do you use ๐— ๐—ถ๐—ฐ๐—ฟ๐—ผ๐˜€๐—ผ๐—ณ๐˜ ๐—˜๐—ป๐˜๐—ฟ๐—ฎ ๐—–๐—ผ๐—ป๐—ป๐—ฒ๐—ฐ๐˜ /๐—”๐˜‡๐˜‚๐—ฟ๐—ฒ ๐—”๐—— ๐—–๐—ผ๐—ป๐—ป๐—ฒ๐—ฐ๐˜?

There are some best practices you should follow.

๐Ÿ›ก๏ธSynchronize only what you need in Entra ID
– No need to synchronize service accounts and nonpresonal accounts
– No need to synchronize on-premise privileged accounts
– No need to synchronize on-premise groups, if for AD purposes only

๐Ÿ›ก๏ธUse High Availability
– Do not rely on one server
– Create another server in staging mode

๐Ÿ›ก๏ธAD Sync service accounts
– Basic user account used to be created in the past
– Check you are using VSA, if remote SQL – GMSA

๐Ÿ›ก๏ธSeamless SSO vs SSO via Primary Refresh Token
– Seamless SSO uses AZUREADSSOACC computer account
– If it exists consider using recommended Primary Refresh Token method
– Both methods are potentially abusable
– If you want to stick with AZUREADSSOACC, follow these best practices:

๐Ÿ›ก๏ธAZUREADSSOACC
– Store the computer account in safe location in Active Directory (do not leave it in the default OU)
– Roll over the kerberos decryption keys every 30 days
– Set encryption type for kerberos only to AES256_HMAC_SHA1