Connect Microsoft 365 (subscribers)

What the connection asks for, what it creates in your tenant, and why.

Publishing requires LlamaSig to create and update transport rules in Exchange Online. You approve that once, on the Microsoft 365 page of the portal. Please read this page before you approve; the permissions are broad by Microsoft's design, and we explain how LlamaSig limits itself.

What you will approve

PermissionTypeWhy LlamaSig needs it
Microsoft Graph User.Read.AllApplicationRead user profiles for signature fields and sending addresses.
Microsoft Graph Organization.Read.AllApplicationRead your organization details, including your initial .onmicrosoft.com domain.
Office 365 Exchange Online Exchange.ManageAsAppApplicationLets LlamaSig sign in to Exchange Online PowerShell as itself, using a certificate, to manage the signature rules.
Exchange Exchange.ManageDelegated, during setup onlyLets you, as an administrator, create the restricted Exchange role described below.

What LlamaSig creates in your tenant

  • An Exchange management role named LlamaSig Transport Rules, created as a child of the built-in Transport Rules role and restricted to the transport-rule commands LlamaSig uses: Get-TransportRule, New-TransportRule and Enable-TransportRule. When you allow editing and removal, the role is later extended with Set-TransportRule and Remove-TransportRule (the portal shows an Update Exchange permissions button).
  • A role group named LlamaSig Transport Automation that contains only LlamaSig's service principal, LlamaSig Platform.
Be aware: Exchange role permissions for transport rules apply to the whole organization; Microsoft does not offer a way to scope them to a single rule. LlamaSig is built to change only rules it created: each carries a marker in its comments, and LlamaSig refuses to update or remove any rule whose marker or content does not match what it last published. It also never sets "stop processing more rules", so your other mail-flow rules keep working.

Steps in the portal

  1. Choose your options

    On the Microsoft 365 page, tick Allow automatic Exchange rule management to let LlamaSig create, update and remove its rules. Tick Enable Exchange customization if needed only if Microsoft asks for it: in some organizations Exchange must run a one-time "organization customization" before a custom role can be created, and Microsoft does not document a way to undo it.

  2. Connect Microsoft 365

    Select Connect Microsoft 365, sign in as an administrator who can grant organization-wide consent (for example, a Global Administrator) and approve the permissions above.

  3. Complete Exchange setup

    Back in LlamaSig, select Complete Exchange setup. LlamaSig shows a short code. Open login.microsoft.com/device, enter the code and sign in with an Exchange administrator account. LlamaSig then creates the role and role group and verifies the connection.

How LlamaSig signs in to Exchange

LlamaSig signs in to your tenant with a certificate held by the LlamaSig service. No password or secret from your tenant is stored. Revoking consent or removing the role group ends LlamaSig's access immediately. How to remove LlamaSig.

Publisher verification

Microsoft shows an "unverified" label for apps whose publisher has not completed Microsoft's publisher verification. LlamaSig has not completed it yet, so you will see that label on the consent screen. The application is LlamaSig Platform, application ID 1ecb8378-ea0d-45fa-96ce-f876e048689a; check that the ID matches before you approve.

Related guides

Was this helpful? If something is unclear or out of date, tell us. We will fix it.