Microsoft OAuth (Third-Party Account) — Setup Guide

Overview

Use this guide to connect Microsoft 365 to MinuteView by creating an Azure app registration. This will let MinuteView workflows use your Microsoft account to:

• Access SharePoint/OneDrive files
• Read and send email
• Access and send Teams chats/messages
• Manage calendar events

⚠️ This setup is for Delegated (user sign-in) accounts. The account signs in once, and MinuteView securely stores a refresh token so it can keep working without you re-signing in.

---

Network Requirements

Even though each user signs in through their own browser, the MinuteView server is what talks to Microsoft after the login. When the user is redirected back after signing in, the server exchanges the authorization code for a token by calling Microsoft directly — and from then on it silently refreshes that token in the background using the stored refresh token, with no browser involved. This means the MinuteView server must have outbound internet access to the following domains.

Required Firewall / Proxy Whitelist

The following domains must be accessible via HTTPS (port 443) from the server where MinuteView is installed:

Domain	Purpose
login.microsoftonline.com	OAuth token exchange, background token refresh, and authorization
graph.microsoft.com	Microsoft Graph API calls (SharePoint, OneDrive, Teams, mail, calendar, user profile, etc.)

Server Access Required

These domains must be reachable from the server, not just from the user's PC. The user's browser only handles the initial sign-in. The token exchange, the ongoing refresh of expired tokens, and every subsequent Graph API call are all made server-side. If the server cannot reach these domains, the account will appear to sign in successfully in the browser but then fail with a connection error, or silently stop working once the first token expires.

If this account is also used for Business Central (the optional Financials.ReadWrite.All permission above), the server additionally needs outbound access to api.businesscentral.dynamics.com. The token itself is still issued by login.microsoftonline.com.

---

Step 1 — Register the App in Azure

1. Go to the Azure Portal → App registrations → New registration.

2. Give it a name, e.g. MinuteView (Delegated).

3. Choose Supported account types:

   • Usually “Accounts in this organizational directory only” (single tenant).

4. Add a Redirect URI (type: Web):

   • https://your-domain/MinuteView/PageGeneral/ServiceCallback.aspx

5. Click Register.

---

Step 2 — Collect App Details

From the app’s Overview page, copy:

• Application (client) ID
• Directory (tenant) ID

Then create a Client secret:

1. Go to Certificates & secrets.
2. Click New client secret.
3. Copy and store the generated secret securely (you’ll need it for MinuteView).

---

Step 3 — Add Required Permissions

Go to API permissions → Add a permission → Microsoft Graph → Delegated permissions. Add:

Files & SharePoint

• Files.ReadWrite.All
• Sites.ReadWrite.All

Mail

• Mail.Read
• Mail.Send
• Mail.Read.Shared

Teams

• Chat.ReadWrite
• ChannelMessage.Send
• TeamsActivity.Send
• User.ReadBasic.All
• People.Read
• User.Read

Calendar

• Calendars.ReadWrite

Dynamics 365 - Business Central

• (optional) Financials.ReadWrite.All if required for Business Central Integration

Sign-in & Profile (REQUIRED)

• openid
• profile
• email
• offline_access

✅ Don’t forget to Grant admin consent so your users don’t get blocked.

---

Step 4 — Enter Details into MinuteView

In MinuteView, when adding a Microsoft OAuth account:

• Paste the Client ID, Tenant ID, and Client Secret
• Enter your Redirect URL (same as Azure registration)
• Save and test the connection

MinuteView will handle the rest:

Now when you add a node to a workflow that requires this account, you will see a red icon for Microsoft. simply click the icon, it will ask you to sign in the first time, the next time it will be green and ready to use.

---

Step 5 — Test the Connection

Try running a workflow node that uses Microsoft data. For example:

• SharePoint file listing
• Sending a test email
• Reading calendar events

If it works, your setup is complete.

---

Troubleshooting (Quick Fixes)

• Redirect URI error → Double-check the URL matches exactly in both Azure and MinuteView.
• Insufficient privileges → Ensure permissions are added and admin consent is granted.
• Teams actions failing → Some Teams features may require Application permissions. For user workflows, stick with Delegated.

---

Summary

• Register an app in Azure
• Add the required Microsoft Graph delegated permissions
• Enter IDs and secrets into MinuteView
• MinuteView stores tokens and handles refresh automatically