Empire Teas CRM — Azure & Pipedrive Configuration Session Notes
Date: 10 September 2026 Meeting: Working session — Microsoft Azure (Entra) app configuration + Pipedrive workflow/migration walkthrough Attendees: Shyamin Ayesh, Tharinda Rajapaksha, Dinil Gamage, Biseni Perera, Thilina Abeyrathna, Rukshan Salgado (Altrium); Kavindu Anthony (Empire Teas) Source: reconstructed from the session’s Gemini auto-generated notes (machine-transcribed, not verbatim — treat wording as approximate). Cleaned and reduced here to the items the team can stand behind; anything the auto-notes asserted but attendees do not recall has been left out deliberately (see the migration note below).
Why this file exists: the session stood up the Microsoft Entra app registration and Graph permissions that F20 (mailbox) and F5 (Microsoft login) depend on, and it is the primary record that admin consent was granted and that certificate authentication was chosen after client secrets proved blocked. The concrete, non-secret configuration this produced is maintained in
.forge/design/environments-and-identity.md(§2 identifiers/reply-URLs/permissions, §5 owners & status); this note is the dated account of the decisions behind it.
Summary
Two halves. In the first, Shyamin walked Kavindu through registering the CRM app in Empire’s Entra tenant, adding the Microsoft Graph delegated permissions, and granting admin consent; the intended client-secret credential was blocked by a tenant-wide policy, so the app moved to certificate-based authentication. In the second, Tharinda walked through Empire’s current Pipedrive workflow and migration planning; specifics there are deferred to the Pipedrive audit.
Azure / Entra configuration (decisions taken on the call)
- App registration
CRMcreated in the Empire tenant, single-tenant. Redirect URLs left to be configured (done on the call, then finalised afterwards — see below). - Microsoft Graph delegated permissions added (delegated, not application): sign-in set (
openid,profile,email),offline_access, calendar read/write, mail read/write + send, contacts read/write. The concrete permission list is maintained inenvironments-and-identity.md§2.4. - Admin consent granted for the Empire tenant, so users can subsequently self-connect without further IT involvement. (This is the one-time org-wide consent that client dependency row 4 and the F20-a spec depend on.)
- Client secrets blocked by tenant policy — discovered live while attempting to create one. Resolved by switching to certificate-based authentication (
private_key_jwt): Shyamin to generate and send a certificate for Kavindu to upload to the app registration. This is the origin of the certificate model recorded inenvironments-and-identity.md§2.3 (since 24 Sep 2026: two certificates, one for prod and one non-prod shared by dev, UAT and the laptops). - Reply URLs were configured on the call using values Shyamin supplied, and were finalised after the meeting to the backend Spring Security callback path
/login/oauth2/code/microsoftper environment (api.crm/api.uat.crm/api.dev.crm.empire.lk) — the current table isenvironments-and-identity.md§2.2.
Pipedrive workflow & migration
The session also covered a walkthrough of Empire’s current Pipedrive workflow and migration planning; specifics (record volumes, custom fields, migration handling of records owned by former employees, and the export/pricing-sheet handover) are deferred to the Pipedrive audit and tracked under OQ-26. Nothing from that half is recorded here as settled — the audit and the actual export are the sources of record.
Owed after the session
- [Shyamin Ayesh] Generate and send the Entra login certificate for Kavindu to upload; send name servers / DNS records for the CRM subdomains.
- [Kavindu Anthony] Share the Pipedrive export (leads + contacts) and the current pricing workbook; confirm additional leads held by Pipedrive users.
- Live outstanding for F20-a / F5 login: the certificate upload (above); the dev/uat/prod reply URLs only resolve once those environments and DNS exist (owned by the AWS build-out).
Follow-up, 24 Sep 2026: the certificate item is done — Shyamin Ayesh generated both pairs and Kavindu Anthony uploaded the public halves (environments-and-identity.md §2.3, §5). The DNS records and the environments are still owed.