Microsoft 365 — App Registration
This guide walks a Microsoft 365 administrator through creating and configuring an Azure app registration that Viven uses to ingest content from Outlook, Calendar, OneDrive, SharePoint, and Teams.
Before you begin, confirm your Instance ID with your Viven representative. This value is needed when configuring redirect URIs.
Permission Approach by Phase
| Phase | OneDrive / SharePoint / Teams | Exchange (Outlook Mail & Calendar) |
|---|---|---|
| POC | Delegated scopes (per-user consent) | Application scopes, limited to an allow-listed security group |
| Full rollout | Application scopes | Application scopes |
Application scopes are recommended for the full rollout as they provide a better employee experience and do not require per-user consent flows.
Step 1: Register the Application in Microsoft Entra
This step must be performed by a Microsoft 365 administrator.
- Sign in to the Microsoft Entra admin center
- In the left pane, navigate to Identity → Applications → App registrations and click New registration
- Configure the registration:
- Display name:
DigitalTwin(or your preferred name) - Supported account types: Select based on your deployment:
- Accounts in this organizational directory only (recommended for POC)
- Accounts in any organizational directory (multi-tenant)
- Display name:
- Click Register
After registration, the overview pane will display an Application (client) ID and a Directory (tenant) ID.
Note the Client ID and Tenant ID — both are required by Viven to configure the data source connection.
Step 2: Create a Client Secret
- In your app registration, go to Certificates & secrets → Client secrets → New client secret
- Give it a description and set an expiry
- Click Add
The secret value is only shown once. Copy it before navigating away and share it securely with your Viven representative.