Bilko GCP→Azure Brand Domain Cutover (2026-06-15) — MC #103633
Bilko GCP→Azure Brand Domain Cutover (2026-06-15) — MC #103633
Context
Trigger: GCP billing dead → all-to-Azure migration (CEO directive 2026-06-15).
Scope: Bilko web was already on Azure; api.bilko.cloud was DOWN (HTTP 000, no DNS record). Azure PostgreSQL bilko-demo-pg already populated (63 tables, seed data) so NO DB migration needed — flip-only cutover.
What Changed
1. Cloudflare Worker Redeployment
- Worker:
bilko-edge-proxy - New version:
20b75f53-7e37-43c1-9145-4dc2364e8306 - Rollback target:
707ad1ee-038c-459a-b7aa-588772d1bd49 - Routing:
api.bilko.{cloud,io,company}→bilko-api-demo.purplebeach-f004d490.swedencentral.azurecontainerapps.ioapp.bilko.{cloud,io,company}→bilko-web-demo.purplebeach-f004d490.swedencentral.azurecontainerapps.io
2. DNS Record Added
- Zone:
bilko.cloud(Cloudflare) - Record:
CNAME api.bilko.cloud→bilko-api-demo.purplebeach-f004d490.swedencentral.azurecontainerapps.io(proxied) - Root cause fix:
api.bilko.cloudpreviously had NO DNS record → HTTP 000 failure
3. Configuration Verification
UNLEASH_URLonbilko-api-demoalready correct (Azurebilko-unleash), no change required
Verification (PASS)
Health Check — All 6 Brand Domains
| Endpoint | Status | Response |
|---|---|---|
api.bilko.cloud/api/v1/health |
✅ HTTP 200 | {"status":"ok","service":"bilko-api"} |
api.bilko.io/api/v1/health |
✅ HTTP 200 | {"status":"ok","service":"bilko-api"} |
api.bilko.company/api/v1/health |
✅ HTTP 200 | {"status":"ok","service":"bilko-api"} |
app.bilko.cloud |
✅ HTTP 200 | Next.js HTML (lang="hr"/"sr-Latn"/"bs") |
app.bilko.io |
✅ HTTP 200 | Next.js HTML (lang="hr"/"sr-Latn"/"bs") |
app.bilko.company |
✅ HTTP 200 | Next.js HTML (lang="hr"/"sr-Latn"/"bs") |
Origin Confirmation
- Azure origin confirmed: All responses trace to Azure Container Apps (no GCP markers)
- Auth path live:
HTTP 410 ENDPOINT_RETIRED→ Entra SSO redirect working
Independent Verification
- Proveo E2E verdict: PASS
- Evidence:
/tmp/evidence-103633-flip//tmp/evidence-103633-dns2//tmp/evidence-103633-proveo-e2e/verification.md
Rollback Procedure
If issues arise, rollback the Cloudflare Worker:
wrangler rollback --name bilko-edge-proxy --version-id 707ad1ee-038c-459a-b7aa-588772d1bd49Open Follow-Ups (Low Priority)
- CSP cleanup:
connect-srconapp.bilko.cloudstill allowlists old GCP stage URLbilko-api-stage-dh4m46blja-lz.a.run.app— cosmetic, remove in cleanup PR. - Worker repo commit: Commit
/tmp/bilko-cf-worker/to repoapps/edge-proxy/(MC #100129). - Password rotation: Rotate
bilko_adminPG password (surfaced in session transcript). - Service Principal: Durable SP role grant on
rg-bilko-demo(blocked by harness, needs CEO terminal). - CI migration: Replace dead GCP Cloud Build stage CI with Azure pipeline.
Related Documentation
- DEPLOY-MAP.md: Updated with final Cloudflare Worker route table and DNS state (FlowForge-owned).
- Parent MC: #103633
Published: 2026-06-15 | Author: Skillforge (ALAI Holding AS) | MC: #103633