Re-enable Azure deploy workflows after rotating tenant/SP secrets #127

Why disabled

Both Azure deploy workflows are disabled (2026-05-07) because they were failing on every push with:

AADSTS90002: Tenant '***' not found

Repo secrets were last set 2024-11-21 and the tenant/SP behind them is no longer valid (deleted, rotated, or moved subscriptions).

Disabled workflows

• Build and deploy dotnet core app to Azure Function App - azltops-func (id 54708341)
• Sample App deploy (id 54799403)

To re-enable

1. From a machine logged into the right tenant: az account show --query "{tenantId:tenantId, subscriptionId:id}" -o json
2. Verify the SP behind AZURE_CLIENT_ID still exists: az ad sp show --id <client-id> — if not, create a new federated credential SP for this repo.
3. Update the three repo secrets:

   gh secret set AZURE_TENANT_ID       -R codebytes/load-testing -b "<tenant>"
   gh secret set AZURE_SUBSCRIPTION_ID -R codebytes/load-testing -b "<sub>"
   gh secret set AZURE_CLIENT_ID       -R codebytes/load-testing -b "<client>"   # if rotated
   

4. Re-enable the workflows:

   gh workflow enable 54708341 -R codebytes/load-testing
   gh workflow enable 54799403 -R codebytes/load-testing
   

5. Trigger a test run from a Dependabot PR or a manual workflow_dispatch.

Why it matters

This is a demo repo for the Continuous Load Testing with GitHub Actions talk — the deploy workflows are the demo. Worth fixing before the next time you give the talk.