Setting up the Microsoft integration in Fostr involves connecting your Microsoft 365 environment, authorizing the necessary Graph API and SharePoint scopes, and validating the configuration across Teams, Outlook, and SharePoint services. A successful integration enables meeting insights, calendar visibility, document context, and structured decisions to flow into Fostr automatically.

This section addresses common troubleshooting questions related to connectivity, permissions, and data availability across the Microsoft ecosystem.

Data Not Appearing in Fostr

In some cases, Microsoft data may fail to appear within Fostr workflows. Common causes include:

• Microsoft Teams: Meetings may lack transcripts or recordings if transcription/captioning was not enabled, preventing usable data from being processed.
• Outlook: Events created outside the connected calendar or in unsupported/shared mailboxes may not associate properly with participants.
• SharePoint: Files that are unshared, private, or stored in restricted folders will not be available during sync.
• Permissions: Missing Microsoft Graph or SharePoint API scopes due to incomplete admin consent can block ingest.
• Processing Delays: Microsoft may delay availability of Teams recordings and transcripts for up to 30–60 minutes before they are exposed to APIs.

Bot, App, or Workflow Assistant Not Responding

If the Microsoft Teams bot, Fostr app, or workflow assistant is unresponsive in chat or Outlook mail, the following should be checked:

1. Confirm that the Fostr app is installed and approved in the Microsoft Teams environment for the organization.
2. Verify that the following Microsoft Graph scopes have been consented to:
   1. Chat.Read.All
   2. TeamsAppInstallation.ReadWrite
   3. Mail.Read (for Outlook‑specific features)
   4. Files.Read.All (for SharePoint access)
3. If chat autocomplete or nudges are failing, check whether the bot has permission to run in group chats or guest access channels, where restrictions may prevent its operation.

Incomplete or Missing Summaries and Insights

Occasionally, Fostr summaries, decision points, or extracted insights may appear incomplete or miss expected information. This can occur if:

• The source transcript or email body provides low fidelity (e.g., poor audio quality, overlapping voices, truncated messages).
• Guest users or external participants are excluded from Microsoft Teams transcripts, limiting what can be captured.
• Transcription/caption features were not enabled during the meeting, which reduces extractable content.
• SharePoint links point to documents that are not actually shareable, or metadata is missing/insufficient.
• Emails from Outlook may appear incomplete because forwarded threads, HTML blocking, or message splitting have truncated the accessible dataset.

Note: In nearly all cases, incomplete ingestion or missing insights result from either Microsoft service behavior (permissions, processing delays, retention policies) or configurations at the tenant level (scopes, calendar/mailbox selection, file sharing). Admin review of permissions and environment setup usually resolves these issues.