Adding Almo to Entra – A guide for IT Admins

Introduction

Almo is a Microsoft AppSource Outlook add-in. Before users in your organisation can sign in, an IT Administrator needs to grant admin consent once, organisation-wide. This consent is granted via Azure Portal and Entra.

This page explains what permissions Almo requires, why, and how to grant them.

Security Certification

Almo is listed on Microsoft AppSource, Microsoft’s verified marketplace for Outlook add-ins. Before any add-in is published on AppSource, Microsoft requires it to pass a security and compliance review.

Almo has successfully completed that review.

You can find our listing at https://marketplace.microsoft.com/en-us/product/WA200010090?tab=Overview

Why Almo requires two permission grants

Almo connects Outlook with Azure DevOps. These are separate Microsoft platforms with separate permission models, so Microsoft handles consent for each independently.

Microsoft 365 / Outlook

Almo reads the sender address and thread content of the email it is open next to. This is what allows it to surface relevant Azure DevOps work items alongside the right email.

Azure DevOps

Almo creates, finds, links, and updates work items in the Azure DevOps projects your users connect to.

Each consent screen lists the exact permissions being requested for that system.

Due to Almo working across two Microsoft products, IT Admin consent is required for Almo to be able to connect to both of them. There are two ways to provide this consent. We present both of them below.

Option 1: One-step consent

For most organisations, both grants can be completed using a single link. Clicking it opens a Microsoft-hosted consent screen that covers both permission sets at once.

We recommend that you give consent using this simple one step process made available by Microsoft. You must be signed in as an Entra Administrator.

The URL listed below uses Almo’s client id (0157755d-f51b-4c9b-b65a-c94de797b221) in the parameters. Once approved this ID will also be visible in your Entra setup.

You will see a screen like below once you click this link – https://login.microsoftonline.com/common/adminconsent?client_id=0157755d-f51b-4c9b-b65a-c94de797b221&redirect_uri=https://app.getalmo.com/enterprise-onboarding

After accepting, Almo is authorised for your organisation. Users can install from Microsoft AppSource and sign in 🙂

Option 2 – Manual Two-Step Process

If you prefer to complete the setup within Azure and Entra, please follow instructions in this section.

Part 1 – Approve MS Office Permissions

When a user attempts to sign into Almo for the first time, they will see an “Approval required” screen. They can submit an admin approval request from that screen.

To approve it:

1. Go to portal.azure.com
2. Navigate to Enterprise Applications > Activity > Admin consent requests
3. Select the “My Pending” tab
4. Locate Almo and click “Review permissions and consent”
5. Review the Microsoft 365 permissions list and click “Accept”

The following video illustrates this process

Part 2 – Approve Permissions for Azure DevOps

You can perform this action in either Entra or Azure Portal. We are providing the instructions for completing this in Entra portal

In the Microsoft Entra admin centre (https://entra.microsoft.com)

1. Navigate to Enterprise Applications > All Applications
2. Search for “Almo” and select it
3. Go to Security > Permissions
4. Click “Grant admin consent for [your organisation name]”
5. Review the Azure DevOps permissions list and click “Accept”
6. Click the Refresh button on the screen. You will see the updated permissions

The following video shows this process