This article explains how IT Admins can connect Microsoft Copilot as a source in Josys to visualize AI agents on the AI Agents screen. This setup requires a standard Microsoft 365 integration as a starting point. Because Copilot Studio agents are stored in a Power Platform environment separately from the Microsoft 365 identity data already synced to Josys, additional Microsoft consent and Power Platform application user setup are required in addition to the standard integration.
Overview
This article explains how IT Admins can connect Microsoft Copilot as a source in Josys to visualize AI agents on the AI Agents screen.
This setup requires a standard Microsoft 365 integration as a starting point. Because Copilot Studio agents are stored in a Power Platform environment separately from the Microsoft 365 identity data already synced to Josys, additional Microsoft consent and Power Platform application user setup are required.
See also: About the AI Agents Feature
What the Screen Looks Like After Integration
Once the integration is complete, Copilot Studio agents from the specified Power Platform environment will appear on the Josys AI Agents screen.
Prerequisites
- A Josys Super Admin must complete this integration.
- A Microsoft 365 app integration in Josys must be completed before starting this setup.
If not yet completed, refer to the existing Help Center article first. - Use a Microsoft 365 admin account that can grant tenant-level admin consent.
- You must have Power Platform admin or environment admin access to the environment where the Copilot Studio agents are created.
- The target Power Platform / Dataverse environment must be identified in advance. Copilot Studio supports multiple environments, so confirm which environment contains the agents Josys should detect.
- Create a security role for the Josys application user.
The least-privilege custom role must include read access to thebot,botcomponent, andsystemusertables. Use the System Administrator role for temporary testing purposes only.
Steps
Before You Begin
Complete the Microsoft 365 app integration in Josys.
For full instructions, see this Help Center article.
1. Start the Microsoft Copilot Source Setup
- From the left menu in Josys, click Integrations > External Data Sources.
- Open the AI Agents tab.
- Click the Integrate button for Microsoft Copilot.
- A Microsoft sign-in window will open in a new window.
- After signing in, a permissions confirmation page will appear.
Click the Accept button at the bottom of the page.
2. Get the Environment URL (Instance URL)
- Once consent is complete, you will be returned to the Josys setup flow. The Tenant ID will be populated automatically.
- Sign in to Copilot Studio.
- Click the settings icon in the top right, then click Session Details.
- The Power Platform Environment Details section will appear.
Copy the value shown as Instance URL. - Return to Josys and paste the value into the Environment URL field.
- Click the Send button in the bottom right.
- A confirmation pop-up will appear when the setup is complete.
- ✅ Use this value: Instance URL (e.g.,
https://<environment>.crm7.dynamics.com/) - ❌ Do not use: the Copilot Studio hostname (e.g.,
web.powerva.microsoft.com) - ❌ Do not use: the Environment ID (e.g.,
Default-<tenant-guid>)
3. Create an Application User in the Power Platform Environment
- Follow the "Create an application user" section in Microsoft's help documentation to create an application user.
The application ID isc87fae47-ccbe-408a-94ff-7633fec85801.
Search for and add Josys / AgentBuilderApp. - Optionally, select a business unit.
- Assign a security role and complete the application user creation.
| Field | Recommended Value |
|---|---|
| App | Josys / AgentBuilderApp, selected by name or application ID |
| Name | A clear name such as "Josys Agent Discovery Reader" |
| Business Unit | Default business unit, unless otherwise specified by your Power Platform admin |
| Security Role | Custom read-only role for Copilot discovery (System Administrator may be used temporarily for validation purposes only) |
4. Assign a Security Role
The permissions required for detection are read access to bot, botcomponent, and systemuser.
Assign a role that includes these permissions.
5. Complete the Integration in Josys
-
Agents from the target environment will appear on the Josys AI Agents screen.
Agents registered in Copilot Studio's AI Agents section will be included.If agents do not appear, click the refresh button in the top right and reload the page.
- Hover over an agent to reveal the View Details button.
Click it to see more information. The last active date is pulled from the "Last modified" value in Copilot Studio > Agents.
FAQ
Who should complete this setup?
A Josys Super Admin initiates the setup. A Microsoft tenant admin grants consent, and a Power Platform admin or environment admin creates the application user and assigns the security role.
Is the standard Microsoft 365 integration not enough?
Correct. The standard integration is a required starting point, but detecting agents also requires additional consent and Power Platform application user setup.
Why is the Tenant ID populated automatically?
Microsoft returns the tenant identifier after admin consent is accepted. Josys uses it to associate the source with the correct Microsoft tenant.
What is the Environment URL?
It is the Dataverse instance URL for the Power Platform environment where the agents are created. It appears as "Instance URL" under Session Details in Copilot Studio.
Can I paste the Environment ID instead?
No. The Environment ID and Environment URL are different values. Paste a URL in the format https://<environment>.crm*.dynamics.com/.
Which security role should I use?
For production, use a custom read-only role with the required table permissions. Do not use the System Administrator role as the default for production environments.
What should I check if agents do not appear?
Check the target Copilot Studio environment, the instance URL, the application user, the assigned role, and whether the agents were created in a different Power Platform environment.