Agent 365 Connector

Overview

IFS Loops supports the Microsoft Agent 365 connector as a collaboration capability. This capability allows users to access IFS Loops Digital Workers directly from supported Microsoft applications without switching to the IFS Loops application.

The Agent 365 connector provides a connection between Microsoft Agent 365 Agent Instances and IFS Loops Digital Workers. Each Agent Instance can be mapped to an IFS Loops Digital Worker so that business requests received through Microsoft applications are routed to the appropriate Digital Worker.

Currently, the Agent 365 connector supports collaboration scenarios through:

Microsoft Teams — users can add Agent Instances to a team and invoke them from channels.
Microsoft OneDrive — users can grant access to documents for an Agent Instance and mention the agent in a document comment.

The connector also supports Microsoft Agent 365 observability, providing administrators with visibility into agent sessions, users, executions, tool usage, and failures.

How the Agent 365 connector works

An administrator installs and publishes the IFS Loops Agent 365 Agent Blueprint in Microsoft 365.

An administrator or authorized user creates one or more Agent Instances from the blueprint.

Each Agent Instance is mapped to an IFS Loops Digital Worker.

The Agent Instance is made available in the required Microsoft application.

A user invokes the Agent Instance by explicitly mentioning it.

Microsoft sends the agent event to IFS Loops.

IFS Loops identifies Agent Instance and its mapped Digital Worker.

The Digital Worker processes the request and executes the configured business workflow.

The response is returned to the Microsoft application through the Agent Instance.

Agent activity can be monitored through Microsoft Agent 365 observability.

Agent Instance to Digital Worker mapping

Each Agent Instance has a 1:1 mapping with an IFS Loops Digital Worker.

This allows organizations to create different Agent Instances for different business purposes while keeping Digital Worker configuration controlled in IFS Loops.

Prerequisites

Before configuring the Agent 365 connector, ensure the following prerequisites are available.

Microsoft 365 prerequisites

The Microsoft 365 tenant must be enrolled in the required Microsoft Agent 365 Frontier Preview program.
The user installing and publishing the Agent Blueprint must have the required administrator permissions. A Global Administrator is required for the blueprint installation and permission-granting steps described in this document.
The user responsible for installing and configuring the Agent Blueprint and creating/configuring Agent Instances must have a Microsoft Copilot license assigned to their account.

Note
Contact the IFS Loops support team to obtain the IFS Loops Agent 365 Agent Blueprint build package and any required configuration information.

Required permissions

The following permissions are required for the Agent 365 connector and the IFS Loops Agent Blueprint to operate correctly across identity, collaboration, document access, and observability scenarios.

Agent 365 connector permissions

These Microsoft Graph permissions are required when adding Agent 365 integration in IFS Loops.

Permission

Purpose

User.Read

Allow the connector to read the signed-in user's basic profile information when adding Agent 365 integration in IFS Loops.

User.Read.All

Allows the connector to read basic profile information of users interacting with the agent, such as user ID, name, and email, as well as Agent Instance details, including ID, name, email, and application ID.

offline_access

Allows the connector to securely maintain refresh tokens, eliminating the need for interactive sign-in for every request.

IFS Loops Agent Blueprint permissions

These delegated permissions are requested when installing and publishing the IFS Loops Agent 365 Agent Blueprint in Microsoft 365.

Permission

Purpose

AgentData.ReadWrite

Allows the Agent 365 agent to read and update the data needed to process conversations and maintain conversation context.

Connectivity.Connections.Read

Allows the agent to view the connections configured for the agent.

Agent365.Observability.OtelWrite

Allows the Agent 365 agent to send monitoring and telemetry information to Microsoft Agent 365 Observability.

Sites.Read.All

Allows the agent to read documents and list items from SharePoint sites and content that Agent Instance has access to.

Files.Read.All

Allows the agent to read files that Agent Instance has access to, so attachments and document content can be processed by the Digital Worker.

1. Configure the Agent 365 connector

The Agent 365 connector is used to connect Microsoft Agent 365 capabilities with IFS Loops Digital Workers.

Step 1 – Open IFS Loops

Sign in to IFS Loops.
From the menu bar, select Connectors.

Click Add Integration

In the integration catalog, search for Agent365.

Select Agent 365 from the search results.

Enter a unique name for your integration and click Next.

Click Connect

An authorization window will open to grant the required permissions. Enter your credentials and authorize the requested permissions to continue.
If the details are correct, a confirmation message will appear indicating that the integration has been configured successfully.

Step 2 – Verify the Digital Worker

Before creating the mapping, verify that the required IFS Loops Digital Worker:

Exists in the IFS Loops tenant.
Is enabled and available for execution.
Has the required business workflow and tools configured.

2. Install the IFS Loops Agent 365 Agent Blueprint

Step 1 – Open Microsoft 365 Admin Center

Sign in to the Microsoft 365 admin center using a user with the required administrator permissions.
Navigate to Agents → All Agents.

2. Install the IFS Loops Agent 365 Agent Blueprint

Step 1 – Open Microsoft 365 Admin Center

Sign in to the Microsoft 365 admin center using a user with the required administrator permissions.
Navigate to Agents → All Agents.

Step 2 – Add the Agent Blueprint

Select Add agent.

Select the IFS Loops Agent 365 Agent Blueprint build ZIP package provided by IFS Loops.

Select Next.

Step 3 – Select users or groups

Select the users or groups who should be allowed to create Agent Instances from the IFS Loops blueprint.
Select Next.

Only authorized users should be granted permission to create Agent Instances.

Step 4 – Select the template

Select the required template to which the Agent 365 Frontier Preview license should be assigned.
Select Next.

Step 5 – Review permissions

Review the permissions requested by the IFS Loops Agent 365 Agent Blueprint. These permissions allow the agent to operate with the required Microsoft 365 resources and collaboration scenarios. Refer to the Required permissions section earlier in this guide.

Select Next.

Step 6 – Review and publish

Review:

Agent Blueprint information
Users and groups
License/template configuration
Requested permissions
Tenant configuration

20.Select Publish.

After publishing completes successfully, the IFS Loops Agent 365 Agent Blueprint becomes available in the Microsoft 365 environment and can be viewed from the Agent Registry.

3. Create an Agent Instance

An Agent Instance is the actual agent identity that users interact with in supported Microsoft applications. An organization can create multiple Agent Instances from the same IFS Loops Agent 365 Agent Blueprint.

Important — licensing limit
According to the current Microsoft licensing limitation, an organization can create up to 25 Agent Instances in total. This limit applies at the organization level and is not per Agent Blueprint.

Create an Agent Instance

Open the IFS Loops Agent 365 blueprint from the Agent Registry.

Select Add instance.

Enter Agent Instance Name, Agent Instance Alias, and Owner.
Microsoft 365 may take some time to provision the Agent Instance because tenant-level policies and configuration are applied during creation. Wait until the Agent Instance shows as successfully created before continuing with IFS Loops configuration.

4. View Agent Instances

Open the Microsoft 365 admin center.
Navigate to Agent Registry.
Search for IFS Loops.
Open the IFS Loops Agent 365 blueprint.
Select the Instances tab.

Use this view to verify that the required Agent Instance has been provisioned before mapping it to a Digital Worker.

5. Map an Agent Instance to an IFS Loops Digital Worker

After creating the Agent Instance, configure its mapping in IFS Loops using the Agent 365 connector. Each Agent Instance must be mapped to the Digital Worker that will process its requests.

Step 1 – Open Agent 365 configuration

Sign in to IFS Loops.
Open the Agent 365 connector.

Step 2 – Open Agent configuration

Navigate to the Agents configuration tab.
Select Add mapping

Step 3 – Select the Agent Instance and Digital Worker

Select the Agent Instance created in Microsoft 365.
Select the IFS Loops Digital Worker that should handle requests for this Agent Instance.
Save the mapping.

Mapping rule
One Agent Instance can be mapped to only one Agent 365 integration, even if multiple Agent 365 integrations are configured in IFS Loops. The same Agent Instance cannot be mapped or used across multiple Agent 365 integrations

6. Use an Agent Instance with Microsoft Teams

If you want to use the created Agent Instance with Microsoft Teams, follow the steps in this section. Agent Instances can be made available to users in Microsoft Teams in a similar way to adding a normal user to a team.

Step 1 – Open the team

Open Microsoft Teams.
Navigate to the required team.
Open the team's Members section.

Step 2 – Add the Agent Instance

Select Add members.
Search for Agent Instance using its name or alias.
Select the required Agent Instance.
Select Add.

Agent Instance is now available as a member of the team.

Step 3 – Use the Agent Instance in a channel

Open the required channel.
Create a new message
Explicitly mention the Agent Instance.
Enter the business request. Eg.

@Support Agent Please check the status of this customer order.

Important: Agent mention is required
The Agent Instance is invoked only when it is explicitly mentioned. This applies to new channel messages, replies to existing messages, and messages containing attachments. Simply replying to a thread without mentioning the agent does not invoke the Agent Instance.

7. Upload and process attachments from Microsoft Teams

Users can provide attachments to an Agent Instance through Microsoft Teams. The attachment can then be processed by the mapped IFS Loops Digital Worker.

Supported attachment flow

Open the required team and channel.
Ensure the Agent Instance is available in the team.
Create a new message or reply to an existing thread.
Mention the Agent Instance.
Attach the required file.
Submit the message. Eg.

@Support Agent Please review the attached document and summarize the key issues.

Attachment access requirements

The agent must have the required access to read an attachment before the attachment can be processed.
Attachments may originate from Microsoft 365 resources or from the user's collaboration context.
Access and permission requirements can vary depending on where the attachment is stored.
If the required Microsoft 365 permissions have not been granted, the Digital Worker not be able to read the attachment.

8. Use Agent Instance with OneDrive documents

If you want to use the created Agent Instance with Microsoft OneDrive documents, follow the steps in this section. A user can mention an Agent Instance in a document comment and request the Digital Worker to process the document content.

Important: Grant document access first
Before mentioning the Agent Instance in a OneDrive document comment, the specific document must be accessible to the Agent Instance. Do not proceed with the agent mentions until the required document access has been granted.

Step 1 – Provide access to the document

Open the required document in OneDrive.
If the agent does not have access to the document, click Share, search for the agent instance, and share the access (similar to how we share access with other users).

Step 2 – Add a comment

Open the document.
Add a comment in the document.
Mention the Agent Instance in the comment.
Add the business request. e.g.

@Support Agent Please review this document and identify the outstanding action items.

Step 3 – Wait for the Agent 365 event

After the comment is submitted, Microsoft processes the event before sending it to the agent. The event is not delivered immediately. A delay of approximately 2–3 minutes may occur before the event reaches IFS Loops.

Do not assume that the agent failed immediately after posting the comment.

Allow time for Microsoft to deliver the event.

Currently, IFS Loops supports only Excel files for working with OneDrive file comments.

9. Event invocation rules

Agent 365 events are processed when the Agent Instance is explicitly invoked.

Users must mention the Agent Instance whenever they want to trigger an agent operation. This applies even when:

Replying to an existing thread
Continuing a previous conversation
Adding request to a document comment
Sending a request with an attachment

Scenario

Example

New message

@Support Agent Check the status of order 12345.

Reply in a thread

@Support Agent Please also check the customer's previous orders.

Message with attachment

@Support Agent Please analyze the attached spreadsheet.

A reply without the Agent Instance mention is treated as a normal collaboration message and does not invoke the agent.

Event delivery delay
Microsoft may not send collaboration events to IFS Loops immediately. For OneDrive document comments, an event delivery delay of approximately 2–3 minutes may occur. This delay is part of the Microsoft event delivery flow and should be considered during testing and troubleshooting.

11. Monitor Agent 365 observability

Microsoft Agent 365 provides visibility into how IFS Loops Agent Instances are being used. Administrators can monitor information such as:

Agent sessions
Users interacting with agents
Successful and failed operations
Execution time
Agent activity and session details
Tools involved in business workflows
Successful and failed tool executions
Usage of individual Agent Instances

Note:
Observability data not appear immediately in the Microsoft 365 Admin Center for every conversation. The data goes through Microsoft’s internal processing, policies, configuration, and validation checks before it is displayed. As a result, it may take anywhere from a few minutes to several hours for the observability information to become available.

View agent activity