What's included
- Connected in one sign-in. On the client's Data tab, an administrator clicks Connect Microsoft 365 and signs in with a Global Administrator of the client's Microsoft 365. SLApp creates its own app in that tenant, SLApp Helpdesk - Microsoft 365, then takes back the temporary permissions of the sign-in; the client's administrators can see the app and its permissions in Microsoft Entra ID. No app to register by hand in Azure, and no administrator password kept anywhere.
- A secret that renews itself. The app's secret is stored encrypted and renewed automatically 30 days before it expires; if a renewal ever fails, an alert says so before anything stops working.
- Synchronised every 6 hours — users (with their last sign-in when the tenant has Microsoft Entra ID P1), licenses and free seats, MFA registration, administrators and their roles, mailbox usage, verified domains and Secure Score. Sync now when you need fresher data.
- All clients in one list. The Microsoft 365 module, in the Cloud & web group, shows every connected client's tenant at a glance; the client's page gains a Microsoft 365 tab with Users, Licenses, Admins and Domains.
- Everyday user actions from the console — reset a password (generated by SLApp, shown once and never stored), block or unblock sign-in, sign a user out everywhere, create a user with a license, assign or remove a license, and set automatic replies. Nothing runs until a technician confirms it, and every action is recorded in the audit log.
- Alerts that matter — an administrator without MFA (critical), users without MFA, more licenses assigned than paid for or none free while someone waits for one, a mailbox above 90%, and a connection or app secret that needs attention.
- Works with the rest. Domains & email can suggest each client's Microsoft 365 verified domains, and clients connected the old way keep their contacts import and BitLocker keys; Reconnect adds the sync and the user actions, and keeps both.
- A clean exit. Disconnect revokes SLApp's secrets in the client's app and explains how to delete it.
How it works
- 01
Connect once per client
Open the client's Data tab, click Connect Microsoft 365 and sign in with a Global Administrator of the client's tenant. A window shows each setup step as it completes.
- 02
SLApp reads the tenant every 6 hours
With its own app, through Microsoft Graph. Nothing runs in the client's tenant without a technician's click, except renewing that app's own secret.
- 03
Act from the client's Microsoft 365 tab
Find the user, choose the action, confirm — it is done, and it is in the audit log.
- 04
Follow up on the alerts
An administrator without MFA or a mailbox about to fill up shows in Alerts and on the Dashboard, and administrators get an email.
What it needs
- A Global Administrator of the client's Microsoft 365, once, to sign in when connecting — and an SLApp administrator to click Connect. Connecting, reconnecting and disconnecting are for administrators; the user actions are for every technician.
- Microsoft Entra ID P1 in the client's tenant for the last sign-in dates; everything else works without it.
- The app gets Microsoft's User Administrator role, which cannot change most administrator accounts — those stay in the Microsoft 365 admin center.
- If the tenant hides user names in its usage reports, mailbox usage cannot be matched to the users; the page says which setting to change.
Microsoft 365
Users, licenses, MFA and mailboxes of every client's tenant, and the everyday user actions, in one console.