No tenant connection
The workflow itself never signs in to Active Directory or Microsoft 365. Any generated PowerShell runs only after you review and execute it locally.
Teams Ownership Review
Review Teams inventory and ownership gaps using bounded Free checks.
Use this workflow when the job is clear and bounded.
This guide is designed for a single administrative task rather than a broad tenant-wide assessment. It keeps discovery, preparation, any manual change and final verification separate so you can review each step before moving on.
Optional combined ownership summary without requiring a Pro-only step
The workflow, in order.
Opselith does not execute these steps against your environment. Script steps open a reviewed Opselith template; change steps remain explicit so nothing is hidden behind a browser action.
- 01 · SCRIPT
Export Teams inventory
Capture the visible Teams set before reviewing ownership.
Open Export Teams inventory → - 02 · SCRIPT
Export Team owners
Collect the owners returned for each Team.
Open Export Team owners → - 03 · SCRIPT
Find Teams without owners
Identify Teams where the current membership result has no owner.
Open Find Teams without owners → - 04 · ACTION
Assign an approved owner where required
Use the Teams administration path approved by your organization. Opselith does not add or remove owners from the tenant.
- 05 · VERIFY
Re-run the ownerless check
Run the Free ownerless-Team report again and confirm the intended gaps are resolved or documented.
Your tenant stays outside Opselith.
Local progress only
Completed workflow step IDs can be stored in your browser. Identity values, tickets, usernames, domains and generated output are not part of that progress record.
Manual changes stay manual
Where no suitable reviewed script exists, the guide labels the action as a manual change rather than pretending the website performed it.
Recorded trust facts, not a certification.
Opselith separates metadata review, static QA, analyzer evidence and runtime evidence. A missing runtime result or a Pending analyzer state is shown as-is rather than converted into a pass claim.
Workflow catalog, ordered runbook, local-progress and manual-change boundary QA.
A guided workflow is not itself a PowerShell artifact.
No accepted runtime result is recorded for this workflow yet.
browser-guided-runbook · no website tenant connection · tenant output stays outside Opselith.
Trust metadata reviewed for the current 3.0 development contract.
3 referenced scripts · 3 analyzer Passed · 0 Pending
Pending and Not yet recorded are evidence states, not failures. Review the generated script or runbook and validate it in your own environment before production use.
Scripts used by this workflow.
Verify in the authoritative admin tools.
Use the final verification step to confirm the resulting account, membership, licensing or service state in the relevant Microsoft administration portal or Active Directory tooling. Opselith is a runbook and script-generation layer, not the system of record.