You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of security work at Microsoft, we switched our pipelines from PublishToAzureServiceBusV1 (which uses a connection string to publish messages to an Azure Service Bus) to PublishToAzureServiceBusV2 (which uses a federated workload identity).
At around 8/5 at 5pm UTC, these tasks started failing with the following message:
Since then, the errors have been increasing in frequency:
Environment type (Please select at least one enviroment where you face this issue)
Self-Hosted
Microsoft Hosted
VMSS Pool
Container
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Agentless
Relevant log output
Failed to obtain the Json Web Token(JWT) using service principal client ID
Full task logs with system.debug enabled
UNSUCCESSFUL RUN
"Message payload signature was not generated."
Failed to obtain the Json Web Token(JWT) using service principal client ID
SUCCESSFUL RUN
"Message payload signature was not generated."
2024-08-09T17:41:53.0426621Z Received instance ID of: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
2024-08-09T17:41:53.5453278Z Successfully started orchestration with ID 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'.
2024-08-09T17:41:53.6093454Z Getting build status for build ID 10019795
2024-08-09T17:41:54.3673798Z Found build ID '10019795' with status 'Completed'
2024-08-09T17:41:54.8858050Z 'DD-CB-PR' with run ID '10019795' completed with result 'Succeeded'.
New issue checklist
Task name
PublishToAzureServiceBusV2
Breaking task version
2.243.0
Last working task version
2.243.0
Regression Description
As part of security work at Microsoft, we switched our pipelines from PublishToAzureServiceBusV1 (which uses a connection string to publish messages to an Azure Service Bus) to PublishToAzureServiceBusV2 (which uses a federated workload identity).
At around 8/5 at 5pm UTC, these tasks started failing with the following message:
Since then, the errors have been increasing in frequency:
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Agentless
Relevant log output
Full task logs with system.debug enabled
UNSUCCESSFUL RUN
SUCCESSFUL RUN
Repro steps
The text was updated successfully, but these errors were encountered: