Hybrid AD Manager: User Guide
Hybrid AD Manager brings Active Directory Users and Computers, Sites and Services, Domains and Trusts, DNS, Group Policy Management, Entra ID and a set of directory reports into one browser page that looks and behaves like the consoles you know. If you can use ADUC, you can use this. This guide covers what is different and what is new.
Because it is a browser page, the machine in front of you does not have to run Windows. The Microsoft consoles have never shipped for macOS, Linux or iPadOS; this needs nothing installed on your own machine, so a Mac, a Linux desktop or an iPad reaches the same console as everyone else, over HTTPS, with no remote desktop session and no jump box. Safari, Chrome, Firefox and Edge are all fine.
1. Signing in
Open the console URL and choose Active Directory. Use your own account, as user@domain or
DOMAIN\user. Everything you then do runs as you, with exactly your permissions, and is recorded in the
audit log under your name. Entra ID signs in through your Microsoft account. The Local account tab is
for the console's own administrator and only reaches the Settings pages.
Connecting Entra ID. The console reads and changes your Entra ID tenant only as you: it holds no permissions of its own there. Straight after you sign in with Active Directory, the console checks quietly with Microsoft: if your browser is already signed in there, you are connected without a click. Otherwise choose Connect Entra ID (in the banner, the status bar or the user menu) and sign in to Microsoft.
The very first time anyone connects, the organisation itself is connected too: a console administrator chooses Connect Entra ID, a Global Administrator signs in once in the Microsoft window that opens and presses Continue on the page it returns to, and the console sets itself up in your tenant and carries straight on into the administrator's own sign-in. Nobody copies an ID or visits the Entra admin centre. Anyone else who chooses Connect before then is asked to get a console administrator to do it once. From then until you sign out, the cloud side, the Entra ID tool, and the cloud half of Leavers all work with your own Entra rights, Conditional Access and MFA, and Entra's audit log names you. Signing in to the console with Entra ID connects it at the same time. Until you connect, the console shows the on-premises side only; Disconnect Entra ID in the user menu ends it early. This works the same from a Mac, Linux, an iPad or Windows, since the sign-in is Microsoft's own page.
Each Active Directory or Entra ID sign-in takes one licence seat until you sign out, the session expires, or an administrator disconnects it. If all seats are taken the sign-in is refused with a message saying so.
2. The console
The window is laid out like an MMC console: a title bar with the product version, a menu bar, a tree on the left and a list on the right, with a status line at the bottom.
Tab View or Combined View (View menu). Tab View, the default, shows one tool at a time with a tab for each down the left edge. Combined View shows every tool in one tree under Console Root. Both remember your choice per browser. A tool that is not in your licence shows a red mark on its tab.
Domain picker, in the menu bar next to Help, appears when more than one domain is configured and switches the whole console between them.
Menus. File holds Settings, Sessions, Audit log, API tokens, Licence and Sign out. Action opens the actions for the item selected in the tree, the same ones as a right-click. View chooses the layout, which tools are shown, Advanced Features, and the phone layout. Help has About.
Right-click anywhere you would in the Windows consoles: tree items, list rows, empty space in a list.
Find (magnifier, or Ctrl+F) searches the whole domain by name, logon name, UPN or e-mail, plus cloud-only users.
Badges. In the identity column every user carries a coloured dot: green synced (exists on-premises and in Entra ID, linked by ms-DS-ConsistencyGuid), blue cloud-only, amber on-prem only. Edits to a synced account are made on-premises and appear in the cloud after the next sync cycle; the console says so where it applies.
3. Users and Computers
The tree shows the domain with its OUs and containers. Advanced Features (View menu) reveals System, LostAndFound and the other hidden containers, as in ADUC.
New objects. Right-click an OU: New User, Group, Organizational Unit or Computer. The user dialog has the same two pages as ADUC (name and logon, then password and options).
Properties. Double-click or right-click, Properties. The sheets carry the ADUC tabs:
- User: General, Address, Account, Profile, Telephones, Organization, Member Of, Delegation (when the account has service principal names), Dial-in, Published Certificates, Object, Security, Entra ID, Attribute Editor.
- Group: General, Members, Member Of, Managed By, Object, Security, Attribute Editor.
- Computer: General, Operating System, Member Of, Delegation, Location, Managed By, Dial-in, Object, Security, Attribute Editor.
- OU and Contact: their ADUC tabs, plus Security and Attribute Editor.
OK saves and closes; Apply saves; every field maps to one directory attribute. The Attribute Editor tab shows every attribute with its syntax, like ADSI Edit.
Account actions. Right-click a user: Reset password, Disable or Enable, Unlock, Add to a group, Move, Rename, Delete, Copy distinguished name. Reset password can require a change at next logon and unlock at the same time.
Security tab. The permissions on the object. The first view lists the principals and, for the selected one, Allow and Deny boxes for the standard rights and every extended right that applies to that class. Inherited entries show greyed. Advanced opens the full entry list with owner, inheritance and the ability to add, edit or remove entries down to individual attributes. Changing permissions needs the Administrator console role, and, as always, the directory rights to do it.
The Entra ID tab on a user shows how the on-premises and cloud objects are linked, the cloud object ID, and anything the console found doubtful about the match.
4. Entra ID
The Entra ID tool lists cloud users and groups. Cloud-only users can be created, blocked, edited, have their password reset and be deleted from the right-click menu; groups can be created and deleted and their members added and removed. Anything synced from on-premises is changed on the Users and Computers side, and the console says so rather than letting you make a change the next sync would undo. Everything here is read and changed as you, through your own Microsoft sign-in (see Connecting Entra ID in section 1), so you see and can change exactly what your Entra role allows: resetting passwords, for example, needs a role such as Helpdesk, Password or User Administrator.
5. Sites and Services
Sites, subnets, site links, bridges, servers and their NTDS Settings, laid out as in the Windows console. Right-click for New Site, New Subnet, New Site Link, New Site Link Bridge, Move a server to another site, Rename and Delete. Properties edit cost, replication interval, site membership, a subnet's site, and the usual options. Sites live in the forest's Configuration partition, so deleting one needs Enterprise Admins, exactly as in the Windows console.
6. DNS
Zones from the DNS application partitions, with their records. A zone's Properties sheet edits the SOA and name servers. Right-click in a zone's record list to add A, AAAA, CNAME, MX, TXT, SRV, PTR and NS records, edit or delete them. Records take effect on the DC immediately and replicate with the partition.
7. Group Policy Management
The forest, its domains and OUs, and the Group Policy Objects container. Selecting a domain or OU shows the GPOs linked there in link order. Right-click in that list to link an existing GPO or block inheritance; right-click a link for Enforced, Link Enabled, Move Up and Down, and Delete Link. In the GPO list: New GPO, Rename, Delete, and Copy the SYSVOL path. Creating a GPO also creates its SYSVOL folder, which needs the console to run on Windows. Editing the settings inside a GPO (the policy editor) is not part of this version; open it in GPMC from the SYSVOL path shown.
8. Domains and Trusts
The forest and domain functional levels, the FSMO role holders, and every trust with its direction, type, transitivity and SID-filtering state.
9. Reports
A seventh tool, Reports, in the licensed editions. Nineteen reports grouped into Accounts, Passwords, Computers, Groups, Privileged access and Security posture. Pick a category in the tree, or open the Reports root for the full catalogue, and click a report to run it.
Each report shows the headline figures, a chart, and the rows beneath. Where a report takes a period — how long an account has been idle, how old a password is — change the number in the header and press Run. Export CSV saves the rows with the title, when it ran, which domain and domain controller answered, and any warning the report raised. Print / PDF prints the report on its own, without the console around it.
Two things to know about what a report shows you:
- It reads as you. Reports use your own account's rights. Active Directory leaves out objects and attributes you may not read rather than raising an error, so unless you are a domain administrator the report tells you, above the figures, to treat the totals as a floor rather than a complete picture. That warning travels into the CSV as well.
- The privileged reports need privilege. Reports that list who is in the administrative groups are only offered to accounts that are themselves in Domain Admins, Enterprise Admins, Schema Admins or the built-in Administrators. For everyone else they are listed as unavailable with the reason.
An empty report is usually the good answer: no locked-out accounts and nobody with reversible password encryption are results worth having. Where a report finds nothing it says so, and reminds you to check your permissions if you expected rows.
10. Leavers
An eighth tool, Leavers, in the licensed editions, and an Offboard… item on the right-click menu of any user in Users and Computers, sitting next to Disable Account because it is the same intent done in full and written down.
Offboarding somebody by hand means Users and Computers for the account, the Entra portal for the cloud side, and a checklist that lives in somebody's head. This makes it one action, with a record of what it changed and a way to put it back.
What it does, in order
Access is cut first and tidying comes after, so a run that fails half way leaves the account shut rather than tidy:
- Disable the account.
- Replace the password with a long random value that is never shown, kept or written down.
- Disable the Entra ID account, where there is one.
- Revoke Entra ID sign-in sessions. The step everyone forgets: disabling an account stops new sign-ins and does nothing about the mail somebody already has open, because a token that has been issued stays valid until it expires.
- Remove the group memberships, on both sides, recorded before any of them are removed.
- Move the account to the leavers organisational unit.
- Note it in the description, so the object explains itself to somebody reading it in ADUC a year later without this console.
- Hide it from the address lists, where the domain has the Exchange schema extension.
Nothing happens until you have read it
Choosing an account shows the plan, not a confirmation box: every group by name, every step in the order it will run, and the ones that will be skipped with the reason. Then you type the account name to confirm. That is not ceremony — it is the one action in the console that changes eight things at once, and the wrong row selected in a list is how it goes wrong.
Some memberships cannot be removed, and the plan says so rather than promising a clean strip:
- The primary group, usually Domain Users. Active Directory will not remove an account from it. Change the primary group first if the account must come out.
- A group the account is in through another group, which belongs to the nested group and not to the person.
- An Entra ID group synchronised from Active Directory, whose membership lives on-premises and is removed there.
- A dynamic Entra ID group, whose membership is a rule and drops the account when it stops matching.
You are also told about anybody whose manager is the leaver. They are listed and left alone: there is no correct answer this console can pick.
The record, and putting it back
Every run writes a record — what was done, what was kept and why, and the previous values — as a file under the data directory. It is the audit evidence and it is what a restore reads. Records are never deleted by the product; they hold the names and group memberships of former staff on your own server, so the retention policy for that folder is yours to set.
Restore puts the group memberships back on both sides and moves the account to where it was. It does not re-enable the account, on either side, and it cannot recover the password or un-revoke a session — all of which are deliberate, separate actions. Restoring twice is refused.
A second run against a half-done leaver is safe: steps already done are skipped with the reason, and the note in the description is replaced rather than repeated.
Entra ID changes are made as you
The cloud half uses your own Microsoft sign-in for this session (Connect Entra ID; see section 1). The console holds no permissions of its own in your tenant, so without that sign-in it cannot even see the cloud account, and the cloud steps are skipped with the reason; the on-premises half is complete on its own. With it, the rights used are yours, your Conditional Access applies at the moment of the change, and Entra ID's own audit log names you rather than an application. If the application's certificate were ever stolen, it would buy nothing: it only proves to Microsoft that a sign-in is being completed by this console.
The app registration needs no application permissions at all; the delegated ones it needs, and the redirect URI to register, are in the Installation Guide.
Before you start
Set the leavers organisational unit for each domain under Settings, Directory, Leavers. It is checked when you save it. Leave it empty and the move is skipped and says so; everything else still runs.
Offboarding needs the Operator role and a licence that allows writes. The history is readable either way.
11. Phone layout
On a phone or tablet the console switches to a search-first, single-column layout for helpdesk use: search, open a user, see their status and groups, and run the common actions. View, Phone layout forces it on a desktop; the button at the top returns to the full console.
12. Administration pages
Under the user menu or File:
- Settings. The same five steps as the wizard, editable at any time, plus More domains.
- Sessions. Who is signed in, how, since when, from where, and whether they hold a licence seat. Disconnect ends a session at once.
- Licence. What the licence allows, this server's Installation ID and Domain SID (keys are issued for one installation in one domain and only work there), and where to paste a new key. Buttons open the order site with the identifiers filled in: Buy Licence when none is installed (with Start a 30-day trial beside it, until a key has been installed), Renew Licence to add 12 months, and Add seats or domains (shown while more than six months remain) to raise the counts for the rest of the current term at a pro-rata price. The console refuses a key for another server or domain, an upgrade key issued for a different licence, and a key that is older and smaller than the one installed.
- Audit log. Every sign-in, read and change, by day and by actor, with what changed but never the values of secrets.
- API tokens. Personal tokens for scripts. A token can never do more than the person who created it.
13. Roles at a glance
| Role | Can |
|---|---|
| Reader | Browse every tool, open property sheets, search, read their own audit entries |
| Operator | Everything Reader can, plus create, change, move, rename and delete objects, DNS records, sites and GPO links, and offboard a leaver |
| Administrator | Everything Operator can, plus change permissions, manage the licence, sessions and settings |
The directory's own permissions always apply on top: the console shows what your account can see and refuses what your account cannot do, with the directory's own reason.