Quickstart

Use a small group and test tickets for your first InboxLink pilot.

1. Create your Microsoft application

An Entra application administrator creates a single-tenant registration in your company’s tenant. Follow Microsoft Entra setup to configure the two redirect URIs, delegated scope and directory-role claim.

2. Configure HaloPSA

Create a native Halo OAuth application using HaloPSA API setup. Keep the Halo HTTPS origin and public client ID ready.

3. Register your company

Open signup. Enter the company details, Microsoft tenant and application IDs, and HaloPSA settings. Continue with a Microsoft application administrator from your organisation. InboxLink verifies the signed Microsoft identity and creates your workspace and 14-day trial.

Save the workspace link and code returned by signup. The code is your Microsoft tenant ID; users enter it once in Outlook. It is public configuration, not a password.

4. Deploy to your pilot group

Download the add-in manifest from https://inboxlink.app/manifest.xml and deploy it to your pilot group from the Microsoft 365 admin centre. Open InboxLink in Outlook, enter the workspace code and select Connect to HaloPSA. Each user signs in through your Microsoft registration and their own HaloPSA account.

Add one received email to a test ticket and send a reply to check both directions. Test Classic Outlook, New Outlook and Outlook on the web where your users need them. Owners and admins can manage seats and the plan from your workspace.

Hosting the service yourself

Operators can use the repository’s container and Azure deployment instructions. Configure DATABASE_URL, HALO_TOKEN_ENCRYPTION_KEY and PUBLIC_BASE_URL, apply migrations and verify readiness before accepting traffic. Company registrations are entered at signup; the hosted service does not require a global Microsoft client ID. See PostgreSQL deployment for database configuration.