Fostr’s Microsoft integration connects key tools from the Microsoft ecosystem, including Teams, Outlook, and SharePoint, into your operational workflows. This page explains how access is authorized, what permissions are required across different Microsoft services, and who within your organization can view or manage synced data once the integration is established.

Credentials and Access

The Microsoft integration requires secure application credentials that authorize Fostr to connect with Microsoft Graph and SharePoint APIs. During setup, organizations typically provide:

• Client ID
• Client Secret
• Tenant ID
• App ID (used for Teams bot registration, Outlook access, or SharePoint application contexts)

This integration operates at the tenant level and must be authorized by a Microsoft 365 administrator. Tenant-level authorization allows Fostr to ingest organization-wide data across services like Teams, Outlook, and SharePoint, depending on the scopes granted during setup.

All credential information is encrypted and stored within Fostr’s internal systems, inside the customer’s integration record. Access is tightly restricted and protected across all environments.

Administrator consent is required for specific Microsoft Graph and SharePoint scopes that support Fostr workflows. Common examples include:

• OnlineMeetings.Read
• Calendars.Read
• User.Read.All
• Chat.Read.All

User emails are not made public. Instead, Fostr leverages internal user IDs and organizational context for secure identity matching.

Permissions and Visibility

Once activated, the Microsoft integration enables Fostr to surface structured outputs and insights from across the Microsoft 365 suite. Data becomes available inside workflows where it adds operational context or supports action execution. Examples include:

• Teams: meeting summaries, decisions, and key discussion points (when transcripts or recordings are available)
• Outlook: calendar event metadata and time-sensitive insights
• SharePoint: shared dashboards or documents, if linked into workflows or customer records
• Workflows: contextual nudges, tasks, or prompts tied directly to user activity in Microsoft tools

Visibility into this data follows Fostr’s organizational roles, combined with Microsoft’s own permission model. For example:

• Meeting participants, attendees, or document collaborators can see the content that relates to them.
• Managers and goal owners may be able to view summaries or insights that are relevant to their teams.

Currently, granular role/channel scoping cannot be applied inside Fostr. Visibility is inherited from Microsoft itself (such as calendar invitees, Teams channel memberships, or SharePoint sharing settings).

Automation and Ongoing Management

No ongoing manual maintenance is required once the integration is enabled. After initial setup, including OAuth approval and, if applicable, registration of Teams bots or apps, Fostr automatically manages synchronization.

The ingestion process runs in the background and requires no additional configuration unless the underlying Microsoft environment changes (e.g., restructuring Teams channels, updating API scopes, or rotating credentials).