trio.so
How-Tos

How to Add a Mac to Active Directory (and When to Skip Binding)

Can you join a Mac to Active Directory? Yes. Steps to bind with Directory Utility, common errors, and why many teams now use Entra ID and SSO instead.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

Yes, you can use Active Directory on a Mac. Bind the Mac to the domain in Directory Utility, or with the dsconfigad command, and domain users can sign in to it. Many teams now skip binding. They sign in with a cloud identity through MDM and single sign on, and keep the Mac off the domain. This guide shows both, so you can choose.

What you need before you bind a Mac

  • DNS that resolves the domain. The Mac must resolve your domain controllers. Point it at your internal DNS, not only a public resolver.
  • Matching time. Kerberos fails when clocks differ by more than five minutes. Use the same time source as the domain.
  • A unique computer name of 15 characters or fewer, to match the NetBIOS limit.
  • An account allowed to join computers to the domain, and the OU where the computer record should go.
  • A network route to a domain controller. Bind on the office network or over VPN.

How to add a Mac to Active Directory in macOS

  1. Open System Settings > Users & Groups. Next to Network Account Server, click Edit, then the add button.
  2. Click Open Directory Utility and authenticate with an administrator password.
  3. Select Active Directory and click the edit (pencil) button.
  4. Enter the Active Directory Domain and a Computer ID. Click Bind and enter the credentials of an account that can join computers.
  5. Choose the Computer OU if you do not want the default Computers container, then click OK.
  6. Restart, then sign in at the login window as DOMAIN\username.

The menu names move between macOS versions, so confirm the path on the version you run.

Bind a Mac to Active Directory from the command line

sudo dsconfigad -add example.local -computer MAC-0142 -username joinaccount -ou "CN=Computers,DC=example,DC=local"
dsconfigad -show

dsconfigad -show prints the current binding. To unbind, run sudo dsconfigad -remove -force -u joinaccount. This is the form you can script in an MDM. Test it on one Mac first.

Common macOS Active Directory errors

  • Cannot find the domain. DNS is wrong. Run nslookup example.local on the Mac.
  • Authentication fails after it worked before. Check the clock, and check that the computer account still exists.
  • The bind fails against newer domain controllers. Check the domain controller event log and the Mac's Kerberos settings.
  • Network home folders are slow or fail. Check the SMB path and the Kerberos ticket with klist.
  • Two Mac accounts for one person. Mobile accounts create a local copy. Decide whether you want a mobile account, and set it the same way on every Mac.

Do you still need to bind Macs to AD?

Often not. Binding is a way to authenticate users to a domain, but a bound Mac gets little else from it. It ties a laptop that leaves the office to a domain controller it may not reach, and the local account can drift from the domain password. Many teams now skip the bind and enroll the Mac in MDM. Users sign in with their cloud identity or a local account that follows it, and the Mac still reaches Active Directory resources through Kerberos single sign on when it is on the network.

Keep binding when you rely on network home folders, on-premises-only apps or legacy file shares that need the Mac to be a domain member. Skip it when your users sign in to Microsoft 365 and the Mac mostly leaves the office.

Manage the Mac and keep identity in Entra ID

For macOS "Active Directory" jobs, the cleaner split is: MDM manages the Mac, and your identity provider handles the user. trio.so enrolls Macs and Windows PCs together, and supports single sign on and Entra ID. See Apple device management.

Managing this across many devices

trio.so enrolls Macs and Windows PCs together, so both sit in one device list. It also supports single sign on and Entra ID for your users. It does not bind a Mac to Active Directory. See Apple device management.

The trio.so device list with Macs and Windows PCs side by side, each with its owner, compliance and last check-in.
Macs and Windows PCs in one trio.so device list.

Related reading: Active Directory migration, multi-tenant Active Directory, Active Directory Certificate Services and macOS network users.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Manage Macs next to Windows PCs in one console

trio.so enrolls Macs and Windows PCs together, and supports single sign on and Entra ID. Start a free trial. No credit card required.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

Yes. Bind the Mac in Directory Utility or with dsconfigad, and domain users can sign in.

Open Directory Utility from Users & Groups, choose Active Directory, enter the domain and computer ID, then bind with an account allowed to join computers.

Not always. Many teams use MDM and Entra ID single sign on instead, and only bind when a legacy app or file share needs the Mac to be a domain member.

Related

From the blog

The related industry news, interviews, technologies, and resources.