Skip to main content

Microsoft Teams Setup

How to package and deploy the Ticku tab app into a client's Teams environment. Audience: the client's Teams/IT administrator.

1. Prepare the App Package​

The package lives in manifest/ and contains:

  • manifest.json — fill in:
    • id — a new GUID for this client's Teams app
    • webApplicationInfo.id — the Azure client ID
    • webApplicationInfo.resource — the Application ID URI (api://<domain>/<client-id>)
    • all domain placeholders — the client's Ticku domain
  • icon-color.png — 192×192
  • icon-outline.png — 32×32

Zip the three files (flat, no folder inside the zip).

2. Upload to Teams​

Teams Admin Center → Teams apps → Manage apps → Upload new app and select the zip.

Alternatively, for a pilot: Teams client → Apps → Manage your apps → Upload an app → Upload a custom app (requires custom app uploads enabled in org policy).

Teams Admin Center → Setup policies — add Ticku to pinned apps for the relevant user groups so it appears in the left rail automatically.

4. Verify SSO​

Open the Ticku tab as a test user. It should load without any login prompt. If users see a consent prompt the first time, an admin can pre-consent: Entra ID → Enterprise applications → Ticku → grant admin consent.

Clock Skew Warning​

Teams SSO validates token timestamps. Machines with clocks off by more than ~5 minutes will see "Session Expired" errors. Ensure client machines sync time (Windows: w32time service running). See Troubleshooting.