Configure InLoox Self-Hosted for Automations with Microsoft 365 and Exchange Online

Learn how to connect InLoox Self-Hosted automations with Microsoft 365 and Exchange Online.

note

This guide is only relevant for InLoox Self-Hosted.

Prerequisites

• This guide applies only to customers using Microsoft 365 with Exchange Online who have configured Azure integration
• InLoox Self-Hosted Server must be installed in version 26.1 or higher
• For Azure integration setup, see Connect Microsoft 365 in InLoox Self-Hosted

Available Automations

With version 26.1, InLoox introduced the following automations:

• Automatic creation of project tasks from flagged emails — Flagged emails are automatically converted to tasks
• Automatic filing of emails from the same conversation — Related emails are grouped together automatically
• Updating project task dates — Start and end dates update automatically when corresponding Outlook calendar entries change

How Automations Work

These integrations use Microsoft Graph API subscriptions. InLoox registers to receive automatic notifications for specific actions in Microsoft 365, Exchange Online, or the Microsoft Graph API.

Examples of monitored actions:

• A new email arrives in the inbox
• An email is flagged
• A calendar entry is moved or updated

After such an action occurs, Microsoft servers automatically call a URL defined by InLoox. This informs the InLoox Server about the change and allows it to react accordingly.

Technical Requirements

The InLoox web server must meet these requirements:

• Publicly accessible via the internet — The defined URL must be reachable from Microsoft's servers
• Valid SSL certificate — A publicly valid SSL certificate is required
• Firewall configuration — The web server must be enabled through your firewall

Infrastructure Responsibility

The configuration of the network and firewall infrastructure is the customer's responsibility. InLoox does not provide infrastructure support.

Security Recommendations

We recommend securing the server publication with additional measures such as:

• DMZ (Demilitarized Zone)
• Reverse proxy
• Application gateway

Contact your network administrator for assistance with firewall and network configuration.

Limitations in Protected Network Environments

In professional corporate environments, web servers are typically located behind a firewall and are not publicly accessible from the internet. In this case, the automations described above cannot currently be used.

If your InLoox server is not publicly accessible:

1. Go to Account Settings in InLoox.
2. Navigate to Integrations.
3. Disable the automations.

This will deactivate the automations and they will not be available to users.

Future Development

InLoox is working on a solution for protected network environments. This solution will initially be tested in a closed beta phase.

If you are interested in participating in the beta program, contact InLoox Technical Support by email: support@inloox.com

The Technical Support team will discuss the next steps with you.

tip

For more details on InLoox integrations, see the Integrations section in the main InLoox documentation.