Approve Lora for Microsoft 365
Let people in your organization invite colleagues from your Microsoft 365 directory, and know exactly what that lets Lora see.
Overview
When someone in your organization invites people to a Lora workspace, they can choose Add from Microsoft 365 and pick colleagues from your company directory instead of typing addresses. To do that, they connect their work account to Lora once.
If your organization only lets admins approve new apps, Microsoft shows Need admin approval at that step. This article is for the admin who gets that request.
Note: This is separate from SSO and SCIM provisioning. Connecting Microsoft 365 to the invite dialog doesn’t change how anyone logs in to Lora, and it doesn’t add anyone to a workspace by itself — everyone invited still gets an invitation email and chooses to join.
What Lora can see
Lora asks for one Microsoft Graph permission: Read all users’ basic profiles (User.ReadBasic.All). It’s a delegated permission, so Lora can only do what the person who connected is allowed to do.
| Lora reads | Lora doesn’t read |
|---|---|
| Each person’s name | Mailboxes, calendars, files or chats |
| Each person’s work email address | Groups, managers or job titles |
Microsoft’s answer includes the basic profile of every user in the directory, guests too. The picker usually leaves guests out of the list. Lora doesn’t store the directory listing. The only addresses it keeps are the ones you choose to invite, and those become invitations in your workspace like any other.
Lora reads the directory only while the invite dialog is open, and it doesn’t store the directory itself. What it keeps for the connection is: an encrypted token, the connecting person’s Microsoft account, and your tenant ID. That stays until the person clicks Disconnect or deletes their Lora account. If you revoke access in Microsoft Entra, Lora can no longer renew its access to your directory, but the access token it already holds keeps working until it expires, usually within about an hour. The stored connection stays until one of those two things happens.
Approve Lora for your organization
Do this once. After that, anyone in your organization can connect without asking again.
Use the link from the invite dialog
- Ask the person to open Administration → Members → Invite → Add from Microsoft 365. When Microsoft asks for approval, Lora shows a link for an admin.
- Open the link and log in with an account that can approve apps for the organization, for example a Global Administrator.
- Review the permission and click Accept.
- Tell the person to go back to Lora and click An admin approved it — connect again.
Use your approval workflow
If you’ve turned on the admin consent workflow in Microsoft Entra, the person can request approval from Microsoft’s own screen instead. You approve it under Enterprise applications → Admin consent requests in the Microsoft Entra admin center.
Check or revoke access
- In the Microsoft Entra admin center, go to Identity → Applications → Enterprise applications.
- Open Lora. Under Permissions, you can review what you approved.
- To take it back, open Properties and click Delete.
After you delete Lora, the invite dialog’s Microsoft 365 picker stops working for everyone in your organization once the access tokens Lora already holds expire, usually within about an hour. After that, the next time someone tries it they’re asked to connect again. Existing workspace members and invitations aren’t affected.
Deleting Lora doesn’t stop anyone from connecting again. If your organization lets people approve apps themselves, the next person who connects approves the permission again, and Microsoft Entra creates the enterprise application again.
Note: Lora uses this same Microsoft Entra app to connect Microsoft Teams. If you delete it, a Teams admin has to approve Lora again the next time they connect Lora to Teams.
If you only want to stop one person’s connection, they can click Disconnect in the picker instead. That removes Lora’s copy of their connection and leaves the app and its permission as they are. To revoke the permission itself, use the steps above.
Stop people from connecting again
To keep anyone from connecting Lora, turn off sign-in for the app instead of, or after, deleting it:
- Open Lora under Enterprise applications, as above.
- Under Properties, set Enabled for users to sign-in? to No and click Save.
Note: Lora’s Microsoft Teams connection signs in with the same app, so while sign-in is off, a Teams admin can’t connect Lora to Teams either. Set it back to Yes to allow that again.
FAQ
Microsoft shows “Need admin approval” when I connect. Your organization only lets admins approve new apps. Send the link that Lora shows to a Microsoft 365 admin, or request approval from Microsoft’s screen if your organization uses an approval workflow.
People who left the company still show up. Lora can’t tell whether an account is still active, so a disabled account can appear in the list. Remove it from the invite list before you send.
A colleague with a work account isn’t in the list. Only people with an email address in their Microsoft 365 profile are listed, and guests are usually left out. Ask them to give you the address, or paste it in instead.
I only have a personal Microsoft account. Personal accounts (Outlook.com, for example) have no company directory. Connect a work or school account instead, or paste email addresses.