--- title: Proactive messaging, reactions, and compute pooling with... description: Building a Foundry hosted agent for Microsoft Teams, the author found that default integration drops message reactions and offers no clean way to send... canonical: https://daily.dev/posts/proactive-messaging-reactions-and-compute-pooling-with-microsoft-foundry-hosted-agents-pttnnis6u twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Proactive messaging, reactions, and compute pooling with Microsoft Foundry hosted agents | daily.dev og:description: Building a Foundry hosted agent for Microsoft Teams, the author found that default integration drops message reactions and offers no clean way to send... og:url: https://daily.dev/posts/proactive-messaging-reactions-and-compute-pooling-with-microsoft-foundry-hosted-agents-pttnnis6u og:image: https://api.daily.dev/og/posts/PtTnnIS6U.png og:image:alt: Proactive messaging, reactions, and compute pooling with Microsoft Foundry hosted agents og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Proactive messaging, reactions, and compute pooling with Microsoft Foundry hosted agents **[Scott Logic](https://daily.dev/sources/scottlogic)** · 16 min read · 1 upvotes · 0 comments ## Summary Building a Foundry hosted agent for Microsoft Teams, the author found that default integration drops message reactions and offers no clean way to send proactive messages or pool compute across users. A bespoke gateway built with the Microsoft 365 Agents SDK sits between the Azure Bot Service and the Foundry Agent Service, translating activities and fabricating developer-role messages to pass reactions through and trigger proactive outreach. The piece also covers an identity-related ConditionalAccessBlocked error encountered during setup, and discusses Microsoft's documented approach to multiplexing compute sessions across users to cut costs from per-user dedicated containers (~$0.15/hour each). ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why does my Microsoft Foundry hosted agent not receive Teams message reactions by default? The default Foundry Agent Service bridges the Azure Bot Service's Activity protocol and the hosted agent's Responses protocol, and that translation is lossy, passing through only message text while dropping reactions and other rich activities. To receive reactions, you need a bespoke gateway between the Bot Service and Agent Service that registers a handler for messageReaction activities and forwards a fabricated narration message to the agent. _daily.dev surfaces practical writeups like this for engineers wiring up Teams bots to Foundry agents._ ### How can a Microsoft Foundry hosted agent send proactive messages to users who haven't messaged it first? Foundry's routines feature only supports a few GitHub and Teams trigger events and runs without user context, so it cannot drive proactive messaging. The workaround is to send the agent a fabricated trigger message from a custom gateway with the "developer" role, so the agent responds as normal but the reply appears proactive to the user since the trigger message itself is hidden from them. _developers wrestling with proactive agent messaging patterns can find hands-on accounts of this on daily.dev._ ### What causes a ConditionalAccessBlocked error when starting a Microsoft Foundry hosted agent? This error occurs when an organization's corporate IT policy blocks agent identities that administrators haven't explicitly allowed, preventing Foundry Agent Service from obtaining a token to start the hosted agent container. The error message states "Agent Identity token issuance is blocked by a Conditional Access policy" and resolving it requires IT administrators to approve the agent's identity blueprint in the Conditional Access policy. _anyone debugging silent Foundry agent failures can compare notes on identity policy gotchas via daily.dev._ ## Similar posts on daily.dev - [What's New in Microsoft Foundry](https://daily.dev/posts/what-s-new-in-microsoft-foundry-izt6m5wlm) · DevBlogs · 0 upvotes · 0 comments - [Building AI apps and agents with Microsoft Foundry](https://daily.dev/posts/building-ai-apps-and-agents-with-microsoft-foundry-tdq7h47dl) · InfoWorld · 0 upvotes · 0 comments - [Microsoft Foundry Now Builds, Deploys, and Governs AI Agents End to End.](https://daily.dev/posts/microsoft-foundry-now-builds-deploys-and-governs-ai-agents-end-to-end--it7nmfneb) · ITNEXT · 1 upvotes · 0 comments - [Microsoft Foundry Tackles the AI Agent Tool Problem Nobody Talks About](https://daily.dev/posts/microsoft-foundry-tackles-the-ai-agent-tool-problem-nobody-talks-about-msoxw2ziz) · DevOps.com · 0 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#azure](https://daily.dev/tags/azure) [View this post on daily.dev](https://daily.dev/posts/proactive-messaging-reactions-and-compute-pooling-with-microsoft-foundry-hosted-agents-pttnnis6u) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Proactive messaging, reactions, and compute pooling with Microsoft Foundry hosted agents","url":"https://daily.dev/posts/proactive-messaging-reactions-and-compute-pooling-with-microsoft-foundry-hosted-agents-pttnnis6u","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/proactive-messaging-reactions-and-compute-pooling-with-microsoft-foundry-hosted-agents-pttnnis6u"},"datePublished":"2026-10-14T13:59:05.073Z","dateModified":"2026-10-14T13:59:30.865Z","description":"Building a Foundry hosted agent for Microsoft Teams, the author found that default integration drops message reactions and offers no clean way to send...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ad219b609a2ada40b9923a7e5d4373f9?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ad219b609a2ada40b9923a7e5d4373f9?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Scott Logic","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Scott Logic","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/65c5cc47d7674fbc83d00599d7b44552","url":"https://daily.dev/sources/scottlogic"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/proactive-messaging-reactions-and-compute-pooling-with-microsoft-foundry-hosted-agents-pttnnis6u","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,azure","timeRequired":"PT16M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Scott Logic","item":"https://daily.dev/sources/scottlogic"},{"@type":"ListItem","position":3,"name":"Proactive messaging, reactions, and compute pooling with Microsoft Foundry hosted agents"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/proactive-messaging-reactions-and-compute-pooling-with-microsoft-foundry-hosted-agents-pttnnis6u#faq","mainEntity":[{"@type":"Question","name":"Why does my Microsoft Foundry hosted agent not receive Teams message reactions by default?","acceptedAnswer":{"@type":"Answer","text":"The default Foundry Agent Service bridges the Azure Bot Service's Activity protocol and the hosted agent's Responses protocol, and that translation is lossy, passing through only message text while dropping reactions and other rich activities. To receive reactions, you need a bespoke gateway between the Bot Service and Agent Service that registers a handler for messageReaction activities and forwards a fabricated narration message to the agent. daily.dev surfaces practical writeups like this for engineers wiring up Teams bots to Foundry agents."}},{"@type":"Question","name":"How can a Microsoft Foundry hosted agent send proactive messages to users who haven't messaged it first?","acceptedAnswer":{"@type":"Answer","text":"Foundry's routines feature only supports a few GitHub and Teams trigger events and runs without user context, so it cannot drive proactive messaging. The workaround is to send the agent a fabricated trigger message from a custom gateway with the \"developer\" role, so the agent responds as normal but the reply appears proactive to the user since the trigger message itself is hidden from them. developers wrestling with proactive agent messaging patterns can find hands-on accounts of this on daily.dev."}},{"@type":"Question","name":"What causes a ConditionalAccessBlocked error when starting a Microsoft Foundry hosted agent?","acceptedAnswer":{"@type":"Answer","text":"This error occurs when an organization's corporate IT policy blocks agent identities that administrators haven't explicitly allowed, preventing Foundry Agent Service from obtaining a token to start the hosted agent container. The error message states \"Agent Identity token issuance is blocked by a Conditional Access policy\" and resolving it requires IT administrators to approve the agent's identity blueprint in the Conditional Access policy. anyone debugging silent Foundry agent failures can compare notes on identity policy gotchas via daily.dev."}}]} ```