Skip to content

JungleMail 365 uses several applications in Microsoft Entra ID: one to sign people in, and one for each kind of connection. Each appears in your tenant, under Enterprise apps, once someone in your organization first consents to it. There you can see what each may access, choose who may use it, and turn it off.

Review them once JungleMail is set up, and again whenever its use changes, for example when a new connection is turned on. Look first at the Microsoft Entra ID connection’s application where a site uses Application permissions: it is the only one that acts without a signed-in person.

Used for Permissions Granted by
Signing in to JungleMail: JungleMail 365 User.Read, offline_access, delegated Each person, or an administrator for everyone
Microsoft 365 sending accounts Mail.Send, User.Read, offline_access, delegated The person who adds the sending account, or an administrator
The Microsoft Entra ID connection, Application permissions GroupMember.Read.All, User.Read.All, and OrgContact.Read.All when the site reads organizational contacts, application A Global Administrator or Privileged Role Administrator
The Microsoft Entra ID connection, delegated permissions GroupMember.Read.All, User.Read.All, and OrgContact.Read.All when the site reads organizational contacts, with offline_access, delegated A Global Administrator, Privileged Role Administrator, Cloud Application Administrator or Application Administrator, then the service account or each editor
The Microsoft Exchange connection EWS.AccessAsUser.All, offline_access, delegated The account that authorizes the connection, or an administrator
The SharePoint connection, archive and subscriber lists SharePoint AllSites.Read, AllSites.Write, AllSites.Manage or Sites.Selected, with offline_access, delegated An administrator the first time, then the account that authorizes
Dynamics 365 CRM Access to your Dynamics 365 environment as an application user A Global Administrator

Delegated permissions act as the person who authorized them, within what that person may do. The Microsoft Entra ID connection’s Application permissions act without a person: they let JungleMail list the members of your groups (GroupMember.Read.All), read the members’ profiles, such as their department and job title (User.Read.All), and include mail contacts that are members of a group (OrgContact.Read.All).

  1. In the Microsoft Entra admin center, go to Entra ID > Enterprise apps > All applications.
  2. Search for JungleMail.
  3. Open an application. Its Properties, Users and groups and, under Security, Permissions hold the settings below.

To see what an application may access, open Permissions: the Admin consent tab lists what was granted for everyone, and User consent what people granted for themselves (Review permissions granted to enterprise applications).

  • To let only some people sign in to JungleMail, open the sign-in application’s Properties, set Assignment required? to Yes and select Save. Then add the people or groups who may sign in under Users and groups. Assigning a group needs Microsoft Entra ID P1 or P2, and doesn’t reach the members of groups nested in it (Manage users and groups assignment to an application). An application that requires assignment needs an administrator’s consent, so grant it first (Grant consent to JungleMail).
  • The same setting on another application limits who can authorize that feature, for example who can add a Microsoft 365 sending account.
  • With Assignment required? set to No and consent granted for everyone, people use JungleMail’s features without asking you.

Global Administrators can sign in to an application whatever its assignment setting (Properties of an enterprise application).

  • Set Enabled for users to sign-in? to No in its Properties. On the sign-in application, nobody can sign in to JungleMail. On a connection’s application, the connection stops working, and so do the newsletters that use it.
  • To take back its permissions, revoke them on Permissions > Admin consent, or select Delete in its Properties. The next person who uses the feature is asked for consent again.

To pause a feature, turn off sign-in rather than revoke: revoking doesn’t stop people from consenting again, where your settings let them (Review permissions granted to enterprise applications).

  • Assign groups, not people. With Assignment required? set to Yes, assign a security group of everyone who signs in to JungleMail: editors, site administrators and anyone else with a role on a JungleMail site. People who only answer approval emails or use the subscription web part don’t need to be assigned. A group with nested groups doesn’t let their members in, so assign the groups themselves.
  • Restrict the sending account application separately. Requiring assignment on it limits who can make a mailbox send newsletters, even among people who may sign in to JungleMail. At EnovaPoint, that could be the site administrators of the Comms, People & Culture and IT Service Desk sites.
  • Review assignments on a schedule. Access reviews ask reviewers to confirm, regularly, that each person still needs an application; they need Microsoft Entra ID Governance (What are access reviews?).
  • Assign the accounts that authorize connections too. On a connection’s application that requires assignment, whoever isn’t assigned can’t authorize it: the service accounts of SharePoint and Microsoft Entra ID, whoever authorizes SharePoint per site, and, with personal accounts, every editor who picks groups. Tell the JungleMail site administrators before you change a connection’s application, and have them test it on Settings > Connections afterward.