Skip to content

SharePoint connection: service account or selected sites

Several features of JungleMail 365 work with SharePoint: SharePoint lists as recipients, SharePoint content and the item picker in emails, archiving newsletters to SharePoint, and SharePoint subscribers. They all go through the SharePoint connection, which a JungleMail site administrator turns on in Settings > Connections and which signs in to SharePoint through JungleMail’s application in Microsoft Entra ID. Its Connection type decides whose permissions JungleMail reads SharePoint with.

For most organizations, choose per site: JungleMail stays out of every site you haven’t granted, and nobody sees more SharePoint content through it than they can open themselves. Choose service account when you would rather set up and review one account than grant sites one by one, and everyone who builds newsletters may use the same content. Don’t use the legacy add-in: Microsoft retired SharePoint add-ins on April 2, 2026, and they no longer work in SharePoint Online (SharePoint Add-In retirement in Microsoft 365).

Connection type Reads with What JungleMail can reach
Microsoft Entra ID app (service account) One service account, for everyone The sites and lists the service account can open, whatever each person’s own permissions are
Microsoft Entra ID app (per site) Each person’s own account Only the sites you grant to JungleMail’s application with PowerShell, and in them what each person can open
Legacy SharePoint App (Add-in) The add-in, which Microsoft retired Nothing new: move to a Microsoft Entra ID app

The connection’s dialog offers the types your organization can use. For the Microsoft Entra ID app types, an administrator grants consent to JungleMail’s application the first time, with Grant Admin Consent in the same dialog, which then says Admin consent is granted.

Service account is the quickest to set up and to review: the account’s SharePoint permissions are the whole story. Everyone who builds newsletters on the site can use whatever the account can open, so give it access only to the sites and lists that newsletters draw on.

Per site keeps JungleMail out of every site you haven’t granted, and respects each person’s permissions inside the sites you have. It uses Microsoft’s Sites.Selected permission (resource-specific consent): you grant each site with a PowerShell command, and each person authorizes their own connection once.

The dialog shows the permissions under Permissions granted to JungleMail 365. They depend on the type and on the feature that asks:

Feature Service account Per site
SharePoint lists and content (Settings > Connections) AllSites.Read + Service Account Sites.Selected + User
Archive lists (Settings > Archive) AllSites.Write + Service Account Sites.Selected + User
SharePoint subscriber lists (Subscriber Management) AllSites.Manage + Service Account Sites.Selected + User

Archive lists and subscriber lists are authorized one at a time, once the SharePoint connection works. For a list on a site granted per site, the PowerShell grant gives JungleMail Write for an archive list and Manage for a subscriber list, instead of Read.

  • Per site, for most organizations. With Sites.Selected, Microsoft allows only what both the application and the signed-in person may do, so JungleMail never exceeds the person’s permissions, nor reaches a site you haven’t granted (Overview of Selected Permissions in OneDrive and SharePoint). It takes a PowerShell grant for every site, and a sign-in from every person who uses SharePoint in JungleMail.
  • Service account, when newsletters draw on a few known sites, everyone who builds newsletters may use their content, and you prefer one account to set up and review. It spares each person an authorization of their own.
  • Legacy add-in, never. A connection still authorized through it no longer works; set it up again with one of the other types (Move SharePoint connections off the add-in).
  • Give the service account only what newsletters need. Visitor access to the sites that newsletters draw on is enough for recipients and content. Add write access only on an archive list, and manage access only on a subscriber list, not on the whole site.
  • With per site, grant each site the lowest role that works. Read for recipients and content, Write for a site with an archive list, Manage for one with a subscriber list. The role is the most JungleMail can ever do on that site, whoever signs in.
  • Choose per JungleMail site if needs differ. Each JungleMail site has its own connections. At EnovaPoint, the Comms site could read the intranet through a service account, while the People & Culture site, whose lists hold personal details, uses per site.
  • Know what stops a connection. A service account’s connection stops when an administrator resets its password or revokes its sessions, until someone authorizes it again (Refresh tokens in the Microsoft identity platform). With per site, a person whose access lapses authorizes again for themselves, and the others are not affected.