Documentation Index
Fetch the complete documentation index at: https://docs.runlayer.com/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- Microsoft 365 admin access to enable Agent 365
- Access to your Runlayer instance
Setup Steps
Enable Agent 365 Access
- Navigate to Microsoft Admin Center > Copilot Settings
- Under Web apps, enable access for all users or specific users
Find Your Environment ID
The Agent 365 servers require your Power Platform environment ID.
- Find your environment ID using Microsoft’s guide
- Save this for the next step
Add Server in Runlayer
- In Runlayer, go to My connectors and click Add connector
- Find a Microsoft Agent 365 (Work IQ) server (e.g., Microsoft Teams (Work IQ), Microsoft Outlook Mail (Work IQ))
- Replace the placeholder environment ID in the URL with your actual environment ID
- Click Create Hosted MCP
- When prompted, sign in with your Microsoft 365 account to authorize access
No Azure AD app registration is required. Runlayer handles OAuth automatically using a shared multitenant application. Users just need to consent during the sign-in flow.
Available Servers
All Microsoft Agent 365 (Work IQ) servers share the same OAuth authorization:| Server | Tools |
|---|---|
| Microsoft Teams (Work IQ) | 25 |
| Microsoft Outlook Mail (Work IQ) | 20 |
| Microsoft SharePoint and OneDrive (Work IQ) | 15 |
| Microsoft SharePoint Lists (Work IQ) | 13 |
| Microsoft Outlook Calendar (Work IQ) | 12 |
| Microsoft 365 User Profile (Work IQ) | 6 |
| Microsoft Word (Work IQ) | 4 |
| Microsoft 365 Copilot Search (Work IQ) | 1 |
| Microsoft 365 Admin Center (Work IQ) | 1 |
Troubleshooting
'Approval required' or consent error during sign-in
'Approval required' or consent error during sign-in
Your Azure AD tenant may require admin consent for third-party apps:
- Ask your Azure AD admin to grant tenant-wide consent for the Runlayer application
- Alternatively, the admin can pre-approve the app in Azure Portal > Enterprise Applications
Agent 365 access not available
Agent 365 access not available
If Agent 365 servers return errors after setup:
- Verify Agent 365 access is enabled in the Microsoft Admin Center (Step 1)
- The API may take a few minutes to propagate after enabling access
Wrong environment ID
Wrong environment ID
If you see connection errors:
- Double-check your Power Platform environment ID
- Ensure you’re using the environment ID, not the tenant ID
- See Microsoft’s guide for finding the correct ID
Next Steps
OAuth Broker Guide
Learn more about OAuth Broker
MCP Custom Servers
Create other custom MCP servers