Microsoft Foundry publish to Teams Bot service error

Question

Microsoft Foundry publish to Teams Bot service error

Delyn Choong 60 Microsoft Employee

Encountered error=Value cannot be null. (Parameter 'TenantId'), please retry. Used this guide for testing Foundry agent publishing: https://learn.microsoft.com/en-us/azure/ai-foundry/agents/how-to/publish-copilot?view=foundry. The process was working previous days. Thank you

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

Sridhar M 5,335 Reputation points Microsoft External Staff Moderator

2026-02-26T10:49:52.6233333+00:00

Hi Delyn Choong

Thank you for bringing this to our attention. We have escalated this issue to our Product Group (PG) team and are currently reviewing the details. The team is actively working on the investigation, and we will update you as soon as we have more information. Thank you for your patience.
Dan 20 Reputation points

2026-02-26T14:35:00.7566667+00:00

Same issue, I have an agent bot service which was configured during the foundry workflow publishing step. This is no longer working for me as of yesterday. Fails even in "Test in web chat" from the bot service with the error Delyn mentions above.
Yingding Wang 5 Reputation points Microsoft Employee

2026-02-26T16:09:43.3266667+00:00

same issue here
Robin Wong Tho Huat 15 Reputation points

2026-02-27T02:32:50.77+00:00

Yes, and it is getting worst. My previously workable agents stopped working in teams and bring out same issue in bot service. Please assist.
Zack Loo 5 Reputation points

2026-02-27T02:37:46.41+00:00

Doesn't work at all, crashed my existing bots, please fix this ASAP
Choo Sheng Kai 5 Reputation points

2026-02-27T02:44:09.8833333+00:00

I am facing this issue as well. Please fix ASAP!
Ding Qiao Wei 0 Reputation points

2026-02-27T02:45:42.52+00:00

My clients are facing this issue as well and are considering switching due to frustration. Please fix asap.
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-02-27T19:31:49.0166667+00:00

Hi Delyn Choong/Yingding Wang and all

Sorry for the trouble.

I am trying to replicate the issue and have tried to reach you via Teams for details needed for engineering ticket creation.

Thank you.
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-02-27T20:38:33.2666667+00:00

Hi Delyn Choong/Yingding Wang and all

I have pushed it to engineering team after replicating and collecting the resource ids. shall keep you posted on this as we progress.

Thank you.
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-02-28T00:05:22.3766667+00:00

Hi Ding Qiao Wei and all

A Hot fix in line to be released from product group to address the issue.

Updated: Hot fix was to be released, at the point of break.

Thank you for your inputs
Delyn Choong 60 Reputation points Microsoft Employee

2026-02-28T02:58:36.51+00:00

Hi thank you for the update. Will check it
kagiyama yutaka 1,320 Reputation points

2026-02-28T03:05:55.69+00:00

I think that ur TenantId=null came from the tenant‑ctx drop in the Foundry→BotSvc hop, so after the hotfix just re‑publish once and tap “Reset session” in BotSvc WebChat to force a fresh token pull that tiny reset fixes the stuck ones.
Chiu Jon 15 Reputation points

2026-02-28T15:40:24.0466667+00:00
Same Here !
my copilot agent that published to Teams always return failed,
and related Bot Service chat test always error in every single chat.

Encountered error=Value cannot be null. (Parameter 'TenantId'), please retry. If issue persists, please use following identifiers in any support request:
Chiu Jon 15 Reputation points

2026-03-01T06:16:41.76+00:00

not work in my case, I recreated bot service and republish Teams agent after that hotfix, is there other possible way can check the current bot service? bot framwork?
kagiyama yutaka 1,320 Reputation points

2026-03-01T06:52:07.31+00:00

Thanks for giving it another try, and I’m sorry it’s still not working as expected. Next could u remove the Teams channel, adding it back, and re‑publishing the agent forces Bot Service to rebuild its auth context and is the most reliable fix for a stuck "TenantId": null". Once the channel is re‑added, let me know what you see so we can confirm it picked up a clean context.
Chiu Jon 15 Reputation points

2026-03-01T10:06:22.96+00:00

Well, I'm doing AI Foundry -> make a AI agent -> then publish into "Microsoft 365 copilot and Teams" which is direct could be use in enterprise Teams as a copilot agent instead being a bot, so there's no channel or reinvite stuff, If you have though that may help, I'm willing to try :)
Chiu Jon 15 Reputation points

2026-03-01T10:10:40.7766667+00:00

Also, In this published process, it would create a breath new bot Service, and that bot service never works, it's spending money, damn ((lol)
Dan 20 Reputation points

2026-03-01T20:53:08.3033333+00:00

Re-tested after the "hotfix", still broken for me.
kagiyama yutaka 1,320 Reputation points

2026-03-01T21:14:09.6566667+00:00

sorry if I misunderstood any part of your setup but i think even with Foundry→Teams publish, Azure still creates a hidden Bot Service (usually bot‑xxxx in the same resource group). Removing and re‑adding its Teams channel rebuilds the tenant‑auth context and usually clears “TenantId = null”. You can find that Bot Service in the same RG as your agent.
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-03-02T02:41:14.6366667+00:00

Hi Delyn Choong,

Please let us know if the proposed workaround on republishing the solution works for you. Review with product group if the issue persists for you.

Thank you.
Delyn Choong 60 Reputation points Microsoft Employee

2026-03-02T03:45:42.22+00:00

Hi Manas, I deleted the bot services, then republished from Foundry Agents > Publish to Teams & M365. I tested in the Bot service Test Web Chat , the error is still the same.

Do see if this helps: please use following identifiers in any support request: ConversationId = ELgTsLozAxF7hx4D6iXcHo-as, activityId = ELgTsLozAxF7hx4D6iXcHo-as|0000000
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-03-02T05:07:03.63+00:00

Hi Delyn Choong

Have updated product group on the same.

Thank you for your inputs.
Zack Loo 5 Reputation points

2026-03-02T07:19:15.7833333+00:00

Still not working, please fix this issue.
Bartosz Ostern 0 Reputation points

2026-03-02T09:06:16.4733333+00:00

I have the same problem, I tried to delete and recreate the bot service, I also created a new bot in foundry and do a new publish nothing works, in copilot/teams the bot cant respond to anything (I wasn't able to generate a response. Send a new prompt or start a new chat.) and in the Azure Bot Service

Encountered error=Value cannot be null. (Parameter 'TenantId'), please retry. If issue persists, please use following identifiers in any support request
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Dan 20 Reputation points

2026-03-04T15:19:14.7433333+00:00

My bot is now working via 'test in web chat' - but I see a new issue when I'm using the direct line channel - Parameter 'userTenantId cannot be null or empty. Anyone else?
Zack Loo 5 Reputation points

2026-03-05T04:53:39.65+00:00

Still have issue with direct line or webchat, please fix this
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-03-05T06:14:30.7166667+00:00

Hi Zack Loo and all

Appreciate your inputs.

Just tested in Canada East region. I am able to get the results.

Could you republish in Canada East and other regions and share your observation.

Checking with Product group on regions selected for hot fix.

Shall keep you posted on this.

Thank you.
JDA 0 Reputation points

2026-03-09T17:18:07.6233333+00:00

I have multiple agents that are working through Chat Interface but receving this error when accessing through Teams Chat Bot Encountered error=Encountered error of type invalid_request_error applied to param conversation with code conversation_not_found and message: Conversation with id 'conv_xxxxx' not found.. If issue persists, please use following identifiers in any support request: ConversationId = a:xxxf, activityId =

Can someone detail this issue or any steps that need to be completed to fix?
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-03-10T09:53:40.28+00:00

Hi JDA

Fix has rolled out fully from product group now.

Please republish from a new resource group to isolate the issue.

If the issue persists, please create a new thread.

Thank you

Answer recommended by moderator

0 additional answers

Sridhar M 5,335 Reputation points Microsoft External Staff Moderator

2026-02-26T10:49:52.6233333+00:00

Hi Delyn Choong

Thank you for bringing this to our attention. We have escalated this issue to our Product Group (PG) team and are currently reviewing the details. The team is actively working on the investigation, and we will update you as soon as we have more information. Thank you for your patience.
Dan 20 Reputation points

2026-02-26T14:35:00.7566667+00:00

Same issue, I have an agent bot service which was configured during the foundry workflow publishing step. This is no longer working for me as of yesterday. Fails even in "Test in web chat" from the bot service with the error Delyn mentions above.
Yingding Wang 5 Reputation points Microsoft Employee

2026-02-26T16:09:43.3266667+00:00

same issue here
Robin Wong Tho Huat 15 Reputation points

2026-02-27T02:32:50.77+00:00

Yes, and it is getting worst. My previously workable agents stopped working in teams and bring out same issue in bot service. Please assist.
Zack Loo 5 Reputation points

2026-02-27T02:37:46.41+00:00

Doesn't work at all, crashed my existing bots, please fix this ASAP
Choo Sheng Kai 5 Reputation points

2026-02-27T02:44:09.8833333+00:00

I am facing this issue as well. Please fix ASAP!
Ding Qiao Wei 0 Reputation points

2026-02-27T02:45:42.52+00:00

My clients are facing this issue as well and are considering switching due to frustration. Please fix asap.
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-02-27T19:31:49.0166667+00:00

Hi Delyn Choong/Yingding Wang and all

Sorry for the trouble.

I am trying to replicate the issue and have tried to reach you via Teams for details needed for engineering ticket creation.

Thank you.
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-02-27T20:38:33.2666667+00:00

Hi Delyn Choong/Yingding Wang and all

I have pushed it to engineering team after replicating and collecting the resource ids. shall keep you posted on this as we progress.

Thank you.
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-02-28T00:05:22.3766667+00:00

Hi Ding Qiao Wei and all

A Hot fix in line to be released from product group to address the issue.

Updated: Hot fix was to be released, at the point of break.

Thank you for your inputs
Delyn Choong 60 Reputation points Microsoft Employee

2026-02-28T02:58:36.51+00:00

Hi thank you for the update. Will check it
kagiyama yutaka 1,320 Reputation points

2026-02-28T03:05:55.69+00:00

I think that ur TenantId=null came from the tenant‑ctx drop in the Foundry→BotSvc hop, so after the hotfix just re‑publish once and tap “Reset session” in BotSvc WebChat to force a fresh token pull that tiny reset fixes the stuck ones.
Chiu Jon 15 Reputation points

2026-02-28T15:40:24.0466667+00:00

Same Here !
my copilot agent that published to Teams always return failed,
and related Bot Service chat test always error in every single chat.

Encountered error=Value cannot be null. (Parameter 'TenantId'), please retry. If issue persists, please use following identifiers in any support request:
Chiu Jon 15 Reputation points

2026-03-01T06:16:41.76+00:00

not work in my case, I recreated bot service and republish Teams agent after that hotfix, is there other possible way can check the current bot service? bot framwork?
kagiyama yutaka 1,320 Reputation points

2026-03-01T06:52:07.31+00:00

Thanks for giving it another try, and I’m sorry it’s still not working as expected. Next could u remove the Teams channel, adding it back, and re‑publishing the agent forces Bot Service to rebuild its auth context and is the most reliable fix for a stuck "TenantId": null". Once the channel is re‑added, let me know what you see so we can confirm it picked up a clean context.
Chiu Jon 15 Reputation points

2026-03-01T10:06:22.96+00:00

Well, I'm doing AI Foundry -> make a AI agent -> then publish into "Microsoft 365 copilot and Teams" which is direct could be use in enterprise Teams as a copilot agent instead being a bot, so there's no channel or reinvite stuff, If you have though that may help, I'm willing to try :)
Chiu Jon 15 Reputation points

2026-03-01T10:10:40.7766667+00:00

Also, In this published process, it would create a breath new bot Service, and that bot service never works, it's spending money, damn ((lol)
Dan 20 Reputation points

2026-03-01T20:53:08.3033333+00:00

Re-tested after the "hotfix", still broken for me.
kagiyama yutaka 1,320 Reputation points

2026-03-01T21:14:09.6566667+00:00

sorry if I misunderstood any part of your setup but i think even with Foundry→Teams publish, Azure still creates a hidden Bot Service (usually bot‑xxxx in the same resource group). Removing and re‑adding its Teams channel rebuilds the tenant‑auth context and usually clears “TenantId = null”. You can find that Bot Service in the same RG as your agent.
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-03-02T02:41:14.6366667+00:00

Hi Delyn Choong,

Please let us know if the proposed workaround on republishing the solution works for you. Review with product group if the issue persists for you.

Thank you.
Delyn Choong 60 Reputation points Microsoft Employee

2026-03-02T03:45:42.22+00:00

Hi Manas, I deleted the bot services, then republished from Foundry Agents > Publish to Teams & M365. I tested in the Bot service Test Web Chat , the error is still the same.

Do see if this helps: please use following identifiers in any support request: ConversationId = ELgTsLozAxF7hx4D6iXcHo-as, activityId = ELgTsLozAxF7hx4D6iXcHo-as|0000000
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-03-02T05:07:03.63+00:00

Hi Delyn Choong

Have updated product group on the same.

Thank you for your inputs.
Zack Loo 5 Reputation points

2026-03-02T07:19:15.7833333+00:00

Still not working, please fix this issue.
Bartosz Ostern 0 Reputation points

2026-03-02T09:06:16.4733333+00:00

I have the same problem, I tried to delete and recreate the bot service, I also created a new bot in foundry and do a new publish nothing works, in copilot/teams the bot cant respond to anything (I wasn't able to generate a response. Send a new prompt or start a new chat.) and in the Azure Bot Service

Encountered error=Value cannot be null. (Parameter 'TenantId'), please retry. If issue persists, please use following identifiers in any support request
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Dan 20 Reputation points

2026-03-04T15:19:14.7433333+00:00

My bot is now working via 'test in web chat' - but I see a new issue when I'm using the direct line channel - Parameter 'userTenantId cannot be null or empty. Anyone else?
Zack Loo 5 Reputation points

2026-03-05T04:53:39.65+00:00

Still have issue with direct line or webchat, please fix this
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-03-05T06:14:30.7166667+00:00

Hi Zack Loo and all

Appreciate your inputs.

Just tested in Canada East region. I am able to get the results.

Could you republish in Canada East and other regions and share your observation.

Checking with Product group on regions selected for hot fix.

Shall keep you posted on this.

Thank you.
JDA 0 Reputation points

2026-03-09T17:18:07.6233333+00:00

I have multiple agents that are working through Chat Interface but receving this error when accessing through Teams Chat Bot Encountered error=Encountered error of type invalid_request_error applied to param conversation with code conversation_not_found and message: Conversation with id 'conv_xxxxx' not found.. If issue persists, please use following identifiers in any support request: ConversationId = a:xxxf, activityId =

Can someone detail this issue or any steps that need to be completed to fix?
Manas Mohanty 15,795 Reputation points Microsoft External Staff Moderator

2026-03-10T09:53:40.28+00:00

Hi JDA

Fix has rolled out fully from product group now.

Please republish from a new resource group to isolate the issue.

If the issue persists, please create a new thread.

Thank you

Answer 1

Delyn Choong 60 Microsoft Employee

Update: The PG team informed me they deployed a hotfix, and I tested my bot service is working now and responding.

kagiyama yutaka 1,320 Reputation points

2026-03-05T06:43:41.1733333+00:00

Hi Delyn glad to hear it’s finally working… really. and Big thanks to everyone who helped in this thread.

if you get a chance, could you share what the PG team said? might help the next person who hits this. and uh pls don’t accept my answer — it wasn’t the fix. just happy it’s all good now .
Zack Loo 5 Reputation points

2026-03-05T06:47:07.19+00:00

The bot on web chat required foundry login, when click but doesn't login got error

Share via

Microsoft Foundry publish to Teams Bot service error

0 additional answers