Fabric Data Agent published to M365 has lost conversational context since yesterday

Thanks for sharing the detailed explanation. This sounds like an issue with the Microsoft 365 published agent rather than the Fabric Data Agent itself, especially since the same agent continues to maintain context correctly within Fabric.

A few things you could try:

- Republish the agent to Microsoft 365 to ensure the latest configuration is synced.

- Verify that conversational memory or session context is still enabled after publishing.

- Clear any cached sessions in Microsoft 365 and start a new conversation to rule out stale session data.

- Compare the agent version deployed in Microsoft 365 with the one currently running in Fabric

- Review the Microsoft 365 and Fabric service health dashboards to check for any recent platform issues or regressions.

If none of these resolve the problem, it may be a recent service-side regression in the Microsoft 365 integration. I would recommend opening a Microsoft support ticket and sharing the conversation IDs, tenant ID, timestamps, and a reproducible example, as that will help the product team investigate more quickly.

Please let us know if you find the root cause. It would be helpful for others who encounter the same behavior.