What's the difference between Available to and Deployed to?

That’s a fair confusion — the labels sound like synonyms, and mixed Slack advice treats them as one toggle. They aren’t.

Here’s what’s going on. Learn is explicit that availability and installation are independent actions. On an agent’s Users tab (and in assign/deploy flows): Available to controls who can find and install the agent (no users / all users / specific users or groups). Installed for (also described as Deployed to in the admin guide) controls who has the agent preinstalled — deploy effectively installs on behalf of the user by accepting Microsoft Entra permissions for them, so the agent is active without a store click. You can make an agent available to Group A while preinstalling it for Group B. Critically, if you install an agent to the entire organisation, it installs for those users even when they weren’t in the original availability audience — Learn calls that behaviour by design. So “Available: Specific group” plus “Installed: Entire organisation” is not a belt-and-braces lockdown; the install wins breadth. Blocking still removes access tenant-wide; pinning only works on deployed agents and is a separate shelf.

Steady before scale here is Pane 07 Cost & Value plus Security: opt-in discovery for experiments, admin deploy only for Wave 0 must-haves you’ve already reviewed. Schofield’s Third Law (historically attributed) again — preinstall is the easiest access path, so treat Deploy as promotion, not a paperwork checkbox.

Options that actually work:

1. Wave 0 pattern: Available to pilot SG, Deployed to the same SG. Users who need it get it without hunting; nobody else sees or receives it. Best Steady default.
2. Available broadly, Deploy narrowly. Catalogue discoverability for trained cohorts; auto-install only for the named owners or champions. Good when you want opt-in culture with a few hard defaults.
3. Deploy to Entire organisation while Available stays “specific.” Surprises Security and burns goodwill — Learn says install can exceed the availability audience.
4. Pin without Deploy, or Deploy without reviewing Data & tools. Pin banners and support tickets; governance theatre either way.

12 Panes action / comms: Tell adoption: Available = can find; Deployed = we installed it for you — pick one story per agent. Tell Security: entire-org install overrides a narrow Available scope — don’t mix them by accident. Leadership: pushed agents are a change programme, not a store listing.

Benefits / risks: Clear levers let you stage rollout without a tenant-wide freeze; mistaken org-wide Deploy is hard to walk back politically; Entra consent on deploy is real privilege acceptance; Available “No users” alone doesn’t undo an existing install — uninstall/block intentionally.

I’d suggest this week: for each agent in the pilot inventory, write two cells — Available audience and Installed audience — and make them match unless you have a documented reason they differ. You’ll get Steady rollout without discovering the override the hard way.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer