This article explains the steps for IT administrators to integrate Microsoft Copilot as a discovery source into Josys and visualize agents on the AI Agents screen. This setup assumes a standard Microsoft 365 integration is already in place. Because Copilot Studio agents are stored in the Power Platform environment separately from the Microsoft 365 identity data that Josys already syncs, additional Microsoft consent and Power Platform application user configuration are required in addition to the standard integration.
Overview
This article explains the steps for IT administrators to integrate Microsoft Copilot as a discovery source into Josys and visualize agents on the AI Agents screen.
This setup assumes a standard Microsoft 365 integration is already in place. Because Copilot Studio agents are stored in the Power Platform environment separately from the Microsoft 365 identity data that Josys already syncs, additional Microsoft consent and Power Platform application user configuration are required in addition to the standard integration.
Reference: About the AI Agents Feature
Target Audience
Josys IT administrators who want to manage AI agents created by employees.
After Integration
Once the integration is complete, Copilot Studio agents within the specified Power Platform environment will be displayed on the AI Agents screen in Josys.
Prerequisites
- A user with Josys Super Admin privileges must perform the integration.
- The app integration with Microsoft 365 in Josys must be completed.
If not completed, please refer to the existing Help Center article first. - Perform the integration using a Microsoft 365 administrator account that can grant tenant-level admin consent.
- You must have Power Platform Administrator or Environment Administrator access to the environment where the Copilot Studio agents are created.
- The target Power Platform / Dataverse environment must be identified (since Copilot Studio supports multiple environments, please confirm beforehand which environment contains the agents Josys needs to discover).
- Create a security role for the Josys application user.
The minimum privilege custom role requires read access to thebot,botcomponent, andsystemusertables. Use the System Administrator role only for temporary testing purposes.
Steps
Assumption
Please complete the Microsoft 365 app integration in Josys.
For details, please refer to this Help Center article.
1. Start Microsoft Copilot Discovery Source Setup
- From the left menu of Josys, click AI Agents.
- From the left menu of Josys, click Integrations > External Data Sources.
- Open the AI Agents tab.
- Click the Integrate button for Microsoft Copilot.
- The Microsoft login screen will open in a separate window.
- Once logged in, the permission confirmation page will open.
Click the accept button at the bottom.
2. Get the Environment URL (Instance URL)
- Once consent is completed, you will return to the Josys setup flow, and the Tenant ID will be automatically populated.
- Log in to Copilot Studio.
- Click the Settings button in the top right, and click Session Details.
- The "Power Platform Environment Details" section will be displayed.
Copy the value of the Instance URL. - Return to Josys and paste it into the Environment URL field.
- Click the Submit button in the bottom right.
- The process is complete when the completion pop-up is displayed.
- ✅ Value to use: Instance URL (e.g.,
https://<environment>.crm7.dynamics.com/) - ❌ Value NOT to use: Copilot Studio host name (e.g.,
web.powerva.microsoft.com) - ❌ Value NOT to use: Environment ID (e.g.,
Default-<tenant-guid>)
3. Create an Application User in the Power Platform Environment
- Create an application user by following the "Create an application user" section on the Microsoft Help Page.
The Application ID isc87fae47-ccbe-408a-94ff-7633fec85801.
Search for and add Josys / AgentBuilderApp. - Optionally, select a business unit.
- Assign the security role and complete the creation of the application user.
| Field | Recommended Value |
|---|---|
| App | Josys / AgentBuilderApp selected by name or Application ID |
| Name | An easily identifiable name, such as "Josys Agent Discovery Reader" |
| Business Unit | Default business unit (unless otherwise specified by your administrator) |
| Security Role | Custom read-only role for Copilot discovery (System Administrator is also acceptable temporarily for verification purposes only) |
4. Assign Security Roles
The permissions required for discovery are read access to bot, botcomponent, and systemuser.
Assign a role that has these permissions granted.
5. Complete the Integration in Josys
-
The agents in the target environment will be displayed on the Josys AI Agents screen.
Agents registered within AI Agents in Copilot Studio are targeted.If they are not displayed, click the refresh button in the top right and reload the page.
- When you hover over an agent, the "View Details" button will appear.
Click it to check the details. The last active date is retrieved from the "Last modified" field within Copilot Studio > Agents.
Frequently Asked Questions (FAQ)
Who performs this setup?
The Josys administrator starts the setup. The Microsoft tenant administrator grants consent, and the Power Platform administrator or environment administrator creates the application user and assigns security roles.
Is the standard Microsoft 365 integration not enough?
Yes. The standard integration is required as a starting point, but agent discovery separately requires additional consent and Power Platform application user configuration.
Why is the Tenant ID automatically populated?
After the administrator consent is completed, Microsoft returns the tenant identifier. Josys uses this to associate the discovery source with the correct Microsoft tenant.
What is the Environment URL?
It is the Dataverse instance URL of the Power Platform environment where the agents are created. It is displayed as "Instance url" in the "Session details" of Copilot Studio.
Can I paste the Environment ID?
No. The Environment ID and Environment URL are different values. Please paste the URL in the format of https://<environment>.crm*.dynamics.com/.
Which security role should I use?
In production environments, use a custom read-only role with the necessary table permissions. Do not use the System Administrator role as the default in production.
What if the agents are not displayed?
Please verify the target Copilot Studio environment, Instance URL, application user, assigned roles, and make sure the agents were not created in a different Power Platform environment.