Fixed-scope diagnostic brief

Azure SWA Custom Domain Validation Diagnostic

A public-safe diagnostic packet for Azure Static Web Apps custom-domain validation that is stuck in Validating or failing with empty errors. Listed fixed scope: $100.

Open ready-to-pay intake Payment activation Proof monitor Acceptance text CSV

Diagnostic evidence map

1. DNS truthCNAME, asuid TXT, resolver spread, TTL, punctuation, and conflict records.

2. Azure stateSKU, region, provisioning state, hostname API output, and redacted correlation IDs.

3. IaC pathBicep/ARM customDomains settings, CLI command path, and deployment history.

4. Escalation packetRepro table, safe next commands, workaround branch, and support-ticket summary.

Fixed scope$100

First $100 path1 paid order

Confirmed money$0

What The Buyer Gets

One evidence matrix that separates DNS state, Azure resource state, IaC state, and support/escalation evidence.
Likely failure buckets for stuck TXT-token validation, cname-delegation failure, orphaned bindings, region/SKU mismatch, and hidden hostname conflicts.
Safe command checklist using redacted `az`, `dig`, ARM/Bicep, and Resource Graph evidence without asking for credentials.
Escalation packet the buyer can paste into official Azure support or a GitHub maintainer reply, with private identifiers removed.

Exact Acceptance Before Payment

The buyer must paste this before any paid work starts:

I accept the Azure SWA Custom Domain Validation Diagnostic fixed-scope terms at $100. I understand work starts only after seller-owned external payment proof exists; I will provide only public or buyer-authorized non-sensitive DNS, CLI, Bicep, and error-output evidence; the deliverable is limited to a diagnostic brief, evidence matrix, likely failure buckets, safe next commands to run, escalation packet, and workaround checklist; and Azure account login, private tenant/subscription access, official Microsoft support, production changes, DNS mutation, guaranteed resolution, ongoing support, or extra revisions are not included unless separately agreed before payment.

Lead Context And Posting Boundary

Lead source: public GitHub issue. Redacted snippet: Static Web Apps custom domain stays in `Validating` forever (dns-txt-token) AND fails with empty `Unspecified` error (cname-delegation) for the same subdomain ### Describe the bug A single Static Web App custom domain cannot be bound using either documented validation method. Both fail in different ways for the *same*

I saw this Static Web Apps custom-domain validation report and can offer a narrow fixed-scope diagnostic brief for $100. I would work only from public or redacted buyer-authorized DNS/CLI/Bicep evidence, without Azure credentials or private subscription access. The deliverable would be an evidence matrix, likely failure buckets, safe next commands, escalation packet, and workaround checklist; it would not replace official Microsoft support.

This draft is not posted. External public comments or direct outreach require explicit send approval. This offer is independent and not affiliated with Microsoft or Azure support.

Proof Boundary

Item	Rule
This page, CSV, lead search, response draft, IndexNow, or issue intake	Counts $0.
Accepted scope plus seller-owned payment URL	Still counts $0 until the external provider confirms payment.
External payment proof, delivery proof, and buyer/platform acceptance	Count only posted, released, payable, or cleared net money after fees/refunds.