Microsoft 365 (Microsoft Graph)
Who this is for: anyone checking what the Liitora library does with Microsoft 365 (Microsoft Graph) before they connect it.
Before you start: nothing, to read this page. To take one of these workflows into use, you need a connection made from the Microsoft 365 (Microsoft Graph) template. See Connect Microsoft 365.
About the template
Section titled “About the template”Reach Microsoft 365 and Entra ID through Microsoft Graph with an app registration in your own tenant. Liitora signs in as the app (no user), and the app can do only what your admin grants it.
Your company fills in only its own values and the names of its secrets. The template fixes the rest, including the hosts a connection made from it may reach, and no workflow can change that.
Library workflows that use it
Section titled “Library workflows that use it”2 library workflows use the Microsoft 365 (Microsoft Graph) template.
Leaver access check
Section titled “Leaver access check”When HR reports that someone has left, check Entra ID and GitHub for access that is still there, open a ticket for each remaining account and email the owner.
This workflow expects the connection m365 to be made from the Microsoft 365 (Microsoft Graph) template.
| What | Details |
|---|---|
| Publisher | Liitora (Published by Liitora) |
| Signature | Liitora signs version 1.0.0 and its content hash sha256:56ebe1168502e98b5279e5b107adee161d98aee6b1da63964d52dbb8ac68301c, and checks both again before it copies the workflow into your company. |
| Connections | github-org: GitHub. Reads organisation membership. Read-only for this workflow.m365: Microsoft 365 (Microsoft Graph). Reads whether the account is enabled. Needs only User.Read.All.service-desk: Your service desk. Creates one ticket per remaining account. |
| Company variables | entra_owner, github_org, github_owner |
| Secrets | None |
| Sends out | |
| Personal data | The leaver’s employee id, user principal name and GitHub handle, sent to your service desk and to the system owners. |
| Checks | Liitora checked that the connections, company variables, secrets and saved state it declares match what the workflow uses. Its 7 tests pass against the real test runner. |
Read the full trust page of Leaver access check.
Quarterly privileged access review
Section titled “Quarterly privileged access review”On the first business day of each quarter, list each privileged Entra ID group’s members, also through nested groups, and email the owner a CSV to confirm or remove them.
This workflow expects the connection m365 to be made from the Microsoft 365 (Microsoft Graph) template.
| What | Details |
|---|---|
| Publisher | Liitora (Published by Liitora) |
| Signature | Liitora signs version 1.0.0 and its content hash sha256:e2ac4df8e88bb921a6481678c23ba7fdb1971c1a821c414356b666e892ebe845, and checks both again before it copies the workflow into your company. |
| Connections | m365: Microsoft 365 (Microsoft Graph). Lists group members. Needs only GroupMember.Read.All and User.Read.All. |
| Company variables | admin_groups |
| Secrets | None |
| Sends out | |
| Personal data | Each group member’s Entra ID, name and user principal name, emailed to that group’s owner. |
| Checks | Liitora checked that the connections, company variables, secrets and saved state it declares match what the workflow uses. Its 5 tests pass against the real test runner. |
Read the full trust page of Quarterly privileged access review.