IAM & Identity
Handle tenant admin, lifecycle work, and mailbox operations without splitting into separate admin consoles.
The value is tenant admin without console sprawl: lifecycle work, mailbox actions, and access changes stay inside the same operator system used for the rest of the customer workflow.
Technicians jump between provider consoles just to finish normal tenant work.
- Password resets, aliases, onboarding, forwarding, and mailbox actions live in separate admin paths
- Customer context falls away while the technician is inside the raw provider console
- Lifecycle work becomes slower and harder to hand off cleanly
Tenant admin stays inside the same MSP operating flow as the rest of the customer work.
- Identity, mailbox, and lifecycle actions stay attached to tickets, docs, backup, and customer context
- Technicians can move from service work into tenant work without rebuilding the same customer picture
- Buyer value becomes faster execution, lower handoff loss, and fewer detached admin paths
Lifecycle, access, and mailbox work stay in one operator-admin flow.
This is the reason the IAM surface matters: tenant work stops being a separate console side quest and becomes part of the same customer-aware operating model.
Create, suspend, offboard, and transfer users with tickets, docs, and protected services still visible.
Password reset, session revoke, admin role changes, and mobile wipe actions stay inside the same workflow.
Aliases, forwarding, delegates, Groups, Teams, and trace work stay attached to the customer record and service thread.
The technician can see the service, documentation, and backup context before pressing the tenant action.
Identity work stays attached to the same support and customer context instead of disappearing into raw provider tools.
The operator can finish mailbox and access work without rebuilding the same customer picture in another tab.
The IAM value is tenant work without admin-console sprawl.
Buyers usually feel this pain as slower onboarding, awkward access cleanup, and too many detached tenant-admin steps. The point is one governed operator path, not one more admin screen.
Included with core VexylCloud
No IAM add-on
- No separate per-seat IAM charge in the current commercial model
- Identity work stays tied to tickets, backup, docs, and customer context
- Useful when MSPs want lifecycle operations without another admin contract
Tenant administration
M365 + Google
- User, mailbox, role, alias, group, and license workflows
- Onboarding and offboarding inside the same operator layer
- One tenant-aware dashboard instead of raw provider consoles for every action
Operator workflow
Lifecycle + mailbox actions
- Password reset, session revoke, forwarding, and delegate access
- Message trace, Teams or group changes, and Drive transfer work
- Cross-tenant script execution from the same operator surface
Products covered
Microsoft 365
Users, licenses, aliases, roles, mailbox actions, Teams membership, and SharePoint visibility.
Tenant adminGoogle Workspace
Users, Gmail forwarding, aliases, Groups, Shared Drives, roles, Drive transfer, and lifecycle handling.
WorkflowLifecycle + mailbox work
Password reset, session revoke, forwarding, delegation, message trace, Teams changes, and Drive transfer stay in the same admin surface.
What technicians can do from the dashboard
Lifecycle Create, update, suspend, and remove users User lifecycle sits inside the same system used for service delivery and customer coordination.
The product already supports user creation, profile updates, access block or suspension, deletion, and tenant-aware onboarding or offboarding workflows.
Access Password, session, and mobile wipe controls Incident response and access cleanup actions do not need a separate admin surface.
Reset passwords, force password change, revoke sessions, and wipe mobile devices from the same dashboard used for the rest of the customer workflow.
Assign Licenses, groups, and admin roles Role and licensing work stays close to the wider tenant context.
- List and assign SKUs
- Add or remove groups and team memberships
- Assign or revoke admin roles
Mailbox Aliases, forwarding, delegates, and trace work Mailbox and collaboration actions remain part of the same operator flow.
Manage aliases, forwarding, delegate access, message trace, spam release where supported, Teams membership, and collaboration context without another detached admin workflow.
Workflow Onboarding and offboarding with tenant context Lifecycle work carries more of the information technicians already need to act cleanly.
Onboarding supports account creation, password handling, license assignment, group membership, and backup acknowledgement. Offboarding supports block or suspension, forwarding, shared mailbox conversion, sign-out, wipe, Drive transfer, and license cleanup.
Execution Cross-tenant PowerShell and Bash scripts Operator actions can stay in one admin workflow instead of opening raw consoles every time.
VexylCloud can execute Microsoft 365 PowerShell and Google Workspace Bash-backed workflows with execution history and tenant context still attached.
See IAM workflows against your tenant stack.
Book a walkthrough if you want Microsoft 365, Google Workspace, SSO, lifecycle actions, and sign-in security mapped against the identity work your team handles every day.