[Bug]: Deploying to PROD failed. BcAuthContext should be a HashTable created by New-BcAuthContext

[LukRod]

AL-Go version

8.1

Describe the issue

Hi,
I need to re-run the Publishing to production git workflow 5 times to successfully publish all bespoke apps.
Every run it install something, but eventually it fails with message: "Deploying to PROD failed. BcAuthContext should be a HashTable created by New-BcAuthContext" If I look on Extension upload status there is nothing wrong.

Expected behavior

It should publish all apps after first run.

Steps to reproduce

wonder if this might be related to the SaaS database size which in this case is around +-250 GB

Additional context (logs, screenshots, etc.)

logs_58292527561.zip

[aholstrup1]

To me it looks like AL-Go can't authenticate with your app registration. From the error below I'm guessing you are using federated credentials but are you sure the app registration in Azure is set up to authenticate from your repo? On your app registration under "Certificates & secrets" you should see your repo and branch listed under "Federated credentials".

2026-02-23T18:51:21.7791322Z InProgress...Renew federated token
2026-02-23T18:51:21.9674574Z Attempting authentication to https://api.businesscentral.dynamics.com/.default using clientCredentials...
2026-02-23T18:51:22.5518985Z Response status code does not indicate success: 401 (Unauthorized). invalid_client
2026-02-23T18:51:22.5524893Z AADSTS70025: The client '***'(Microsoft Azure PowerShell) has no configured federated identity credentials. Trace ID: 2583ed13-6cdc-4ee0-b82e-142b90853900 Correlation ID: f8b3970f-36d0-481b-9b0b-0478b43ba202 Timestamp: 2026-02-23 18:51:22Z
2026-02-23T18:51:22.5527256Z Response status code does not indicate success: 401 (Unauthorized).

https://github.com/microsoft/AL-Go/blob/main/Scenarios/secrets.md#app-registration-service-to-service-authentication

[aholstrup1]

@LukRod Did you manage to make it work?

[LukRod]

Apologize I did not managed to check your suggestion yet. I don't think we are using federated credentials, I think we are using User Impersonation. Unless there is a setting on our customer side and that is why we are only having issues on their environment