Common Setups

Reusable, discovery-first runbooks for connecting Bifrost to common provider systems

Common Setups are end-to-end runbooks for systems that span Bifrost, a provider account, and customer environments. Each setup begins with read-only discovery so you can reuse what is healthy, repair what is incomplete, and create only what is missing.

Microsoft for MSPs

Map customer tenants for Graph and a shared Teams bot. Add optional CSP workspace automation for Partner Center and GDAP.

Start with the Microsoft architecture →

How Common Setups Work

Choose the capabilities you want, not a copied permission list.
Authorize a read-only inventory of the provider, Bifrost, and a development customer.
Review a reuse, repair, or create recommendation for every component.
Approve writes in small phases, with a verification check after each phase.
Complete the few human-only steps such as MFA, tenant-wide consent, and customer approval.
Keep the resulting IDs, mappings, grants, and acceptance results as the operating record.

The runbooks prefer supported APIs and Bifrost workflows over portal screenshots. Microsoft portals remain necessary where Microsoft does not expose an equivalent application-only API.