Skip to main content

🪟 Microsoft 365 Connection

The Microsoft 365 connector is a set of Third Party Credentials linking your Voome platform to your Microsoft Entra (Azure AD) tenant. Once configured, Voome can read your organisation's calendars, rooms, and (optionally) Power BI, SharePoint, and OneDrive content on your behalf.

You set up the connection from a single Voome form (Settings → Platform → Third Party Credentials → add a Microsoft 365 connection). That form is split into three steps. This guide walks you through the matching app registration in Azure and shows where each value goes back into Voome.

What you can enable​

FeatureVoome stepMicrosoft permissions involved
Agenda Microsoft SyncStep 1 (required)Microsoft Graph calendar and rooms
Booking Microsoft SyncStep 1 (required)Microsoft Graph calendar and rooms
Power BI DashboardsStep 2 (optional, delegated)Power BI Service
SharePointStep 2 (optional, delegated)SharePoint sites
OneDrive Document SyncStep 2 (optional, delegated)Microsoft Graph + delegated user
Step 1 is always required

The calendar and booking sync in Step 1 are the foundation of the connection. The Step 2 delegated fields are added on top of Step 1, never as a replacement for it.

Before you start​

You need:

  • A Microsoft Entra (Azure AD) tenant.
  • An account with permission to register applications and grant admin consent in that tenant (typically a Global Administrator or Application Administrator).
  • The Voome connection form open, so you can copy the Redirect URI out of it and copy your Azure values back into it.
Trust direction

Registering the application establishes a one-way trust relationship: your app trusts the Microsoft identity platform, not the other way around.

Part 1 — Register the app in Microsoft Entra (Azure AD)​

1. Register the application​

  1. Sign in to the Azure portal.
  2. If you have access to multiple tenants, use the Directory + subscription filter in the top menu to select the tenant where you want to register the app.
  3. Search for and select Microsoft Entra ID (formerly Azure Active Directory).
  4. Under Manage, select App registrations → New registration.
  5. Enter a display Name, for example Voome Connector.
  6. Choose who can use the application (the sign-in audience). For a single organisation, Accounts in this organizational directory only is the usual choice.
  7. Leave Redirect URI empty for now. You will add it in the next step.
  8. Select Register.

After registration, the Overview pane shows the Application (client) ID and the Directory (tenant) ID. You will copy both into Voome later.

2. Add the Redirect URI​

  1. In Voome, open Step 1 · Connect to Microsoft and copy the Redirect URI. It looks like:

    https://cms.voome.com/signin/ms/voome/

  2. In the Azure portal, open your app (Voome Connector), and under Manage select Authentication.

  3. Select Add a platform → Web.

  4. Paste the Redirect URI you copied from Voome into the Redirect URIs field.

  5. Select Configure.

Copy the URI from your own tenant's form

Always copy the Redirect URI from the Voome form rather than typing it by hand. This guarantees it matches exactly, which Microsoft requires for sign-in to succeed.

3. Create a client secret​

The client secret lets the application authenticate as itself, with no user interaction at runtime.

  1. In your app, select Certificates & secrets → New client secret.
  2. Add a description (for example, Voome).
  3. Choose an expiry. Pick the longest period your security policy allows, since the connection stops working when the secret expires.
  4. Select Add.
  5. Immediately copy the secret Value.
Copy the secret Value now, not the Secret ID

The secret Value is shown only once and cannot be retrieved after you leave the page. Make sure you copy the Value, not the Secret ID: they are different, and Voome needs the Value.

4. Configure API permissions​

  1. In your app, under Manage, select API permissions → Add a permission.
  2. Add the permissions below for the features you plan to use, then select Add permissions for each group.

Required — Microsoft Graph (Delegated)​

These power Agenda and Booking sync, and are needed for every connection.

  • User.Read
  • Calendars.ReadWrite
  • Calendars.ReadWrite.Shared
  • Place.Read.All
  • email
  • offline_access
  • profile

Optional — Office 365 Exchange Online (Delegated)​

Add only if you need to synchronise Exchange Online calendars.

  • Calendars.ReadWrite.All
  • Calendars.ReadWrite.Shared

Optional — Power BI Service (Delegated)​

Add only if you want to embed Power BI content.

  • Dashboard.Read.All
  • Report.Read.All

Optional — SharePoint (Delegated)​

Add only if you need to synchronise SharePoint.

  • Sites.Read.All
  • Sites.Read.Shared

Back on the API permissions page, select Grant admin consent for <your tenant> and confirm. This consents to the configured permissions on behalf of the whole organisation, so individual users are not prompted later.

tip

Granting admin consent is strongly recommended. Without it, the delegated permissions stay in a "not granted" state and the connection may fail.

Part 2 — Enter the values back into Voome​

Return to the Voome Microsoft 365 Connection form and fill it in.

Credentials name​

Give the connection a recognisable name (for example, Contoso Microsoft 365). This is just a label inside Voome.

Step 1 · Connect to Microsoft (always required)​

These values come from the app registration you just created.

FieldWhere to find it
Redirect URIAlready provided by Voome. You pasted it into Azure in Part 1, step 2.
Azure Tenant IdThe Directory (tenant) ID on the app Overview page. Use the literal value organizations for the user delegation process.
Application Id (client_id)The Application (client) ID on the app Overview page.
Application Secret (client_secret)The secret Value from Certificates & secrets (not the Secret ID).

Step 2 · Delegated access (optional)​

Fill this in only for features that act on behalf of a user: Power BI Dashboards, SharePoint, and OneDrive Document Sync.

FieldDescription
Delegated Access UserThe login of the Microsoft user the connection acts as.
Delegated Access PasswordThat user's password.

Test the Power BI connection​

To confirm the delegated credentials can reach Power BI, paste a valid Dashboard or Report ID (in the form XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX) into the Test Power BI connection field and select Test PowerBI.

Save​

Select Save. The connection is now available to the Voome features you enabled.

Troubleshooting​

  • Sign-in fails with a redirect error. The Redirect URI in Azure does not exactly match the one in Voome. Re-copy it from the Voome form and confirm it is added under the Web platform.
  • Permissions show as "not granted". Return to API permissions and select Grant admin consent.
  • The connection worked, then stopped. The client secret has probably expired. Create a new secret in Certificates & secrets and paste its Value into Voome.
  • Power BI test fails. Confirm the Step 2 delegated user has access to the report, the Power BI Service permissions were added, and admin consent was granted.