TC agent doesn't get authorized
We upgraded our TC on-prem to 2026.2 yesterday and from that point on our TC-agent doesn't get authorized any more. This smells like something similar as TW-99003.
Please sign in to leave a comment.
Did you check the following point mentioned in the linked issue?
>according to the logs, the agents on the virtual machines are performing the initial authorization to TeamCity using the same authorization token (the `authorizationToken` property in the `buildAgent.properties` file).
>Am I correct in understanding that this `authorizationToken` value is preconfigured in the image used for these virtual machines?
>If so, the image should be rebuilt without this property set (either leave it empty or remove it entirely).
Please share full logs from the server and agent. You can upload them using https://uploads.jetbrains.com/ and share the Upload ID.
Best regards,
Anton
Hi, we're pretty sure that the token is removed from our base-image, what we also clearly see is that once the agent spins-up a token is being added add runt-time in the buildagent.properties file. In the log you can see that the token is accepted that that we manually need to authorize the agent, this is not really workable for us as we create a fresh agent from each task
see uploaded log file => Upload id: 2026_09_23_2Ab6HEfZuoZPk2PXtN15s1 (file: teamcity-agent.log)
Anton Vakhtel, any update?
Please share the server logs as per my previous message. All logs from the <TeamCity Server Home>/logs would be preferable to have a full picture.
Additionally, please share screenshots of the settings of the Cloud Profile used to start these agents.
Best regards,
Anton
Hi Anton Vakhtel, the server-logs have been uploaded (Upload id: 2026_09_24_QYsvbcw1v5MRDD2Mg8VPqo (file: teamcity-server.log))
you can clearly see in following log that the agent is not getting authorized
[2026-09-23 09:28:13,707] WARN - jetbrains.buildServer.AGENT - The connecting agent "<REDACTED>" {id=0, protocol=unidirectional, host=[<REDACTED>]:9090, version: 238924/NA, agentTypeId=0, registered since 2026-09-23 09:28:13.707} has name of the existing agent, but different authorization token ""; will treat this connecting agent as a new one
[2026-09-23 09:28:13,710] INFO - jetbrains.buildServer.AGENT - Set generated name "<REDACTED>-1" to agent "<REDACTED>" {id=46060}.
[2026-09-23 09:28:13,715] INFO - jetbrains.buildServer.AGENT - New agent authorization token "<REDACTED>" was generated for agent "<REDACTED>-1" {id=46060}
[2026-09-23 09:28:13,722] INFO - gentTypes.AgentTypeManagerImpl - Agent "<REDACTED>-1" {id=46060} has been associated with the agent type with id 3941 using the agent type key: A/A/real-46060
[2026-09-23 09:28:13,725] WARN - jetbrains.buildServer.AGENT - Agent "<REDACTED>-1" {id=46060} is unauthorized on registration
[2026-09-23 09:28:13,727] INFO - jetbrains.buildServer.AGENT - Agent has been registered: "<REDACTED>-1" {id=46060, protocol=unidirectional, host=[<REDACTED>]:9090, version: 238924/NA, agentTypeId=3941, pool=<unknown>, registered since 2026-09-23 09:28:13.707}, not running a build
Yes, I see in the shared teamcity-server.log that the agent is unauthorized. As per my previous message, please share all logs from the <TeamCity Server Home>/logs.
Also kindly share screenshots of the Cloud Profile settings used to start these agents, as requested in the previous message.
Best regards,
Anton
Anton Vakhtel , as requested => 2026_09_25_FvxvZ7CLymuk7P8Dvdo14U
It looks like a side effect of https://youtrack.jetbrains.com/issue/TW-103135 fix.
Azure Integration plugin is a non-bundled plugin, so if the agent side of the plugin is not baked into the build agent image, the agent can't use it to retrieve settings (such as name, auth token, etc.) from the cloud profile. In this case, the agent will default to the standard startup route and will be unauthorized on the first connection. Due to the fix I mentioned above, it also won't be able to pull the plugin from the server to start authorizing, as was possible before the fix.
Once authorized manually, the server issues the upgrade command. The agent then receives the corresponding plugin from the server, retrieves the settings from the cloud profile, and should start working normally.
The recommended approach is to create images from the full agent zip file that has all plugins included. It can be downloaded from the server (Agents > Install Agent page).
For only the Azure Integration plugin, you can find the plugin's zip in <TeamCity Data Directory>/plugins/azure-plugin.zip. It contains the agent and server directories. The agent directory contains azure-plugin-agent.zip, which should be extracted to plugins/azure-plugin-agent on the agent.
Best regards,
Anton
Anton,
Thx, this solved the issue.
Kind regards
Frederik