Integrate MS Teams with Azure OpenAI

-

Integration between Teams and Azure OpenAI can be done by following a few steps.


Create Azure OpenAI Service in Azure Portal 

  1. Sign into Azure Portal at https://portal.azure.com/ and select Azure OpenAI and before you can create a cognitive service, you would need to submit approval document for subscription and pricing tier. Once the document is approved, you will be granted access to create a cognitive service. 

  1. Go to OpenAI Studio at https://oai.azure.com/ with credentials that have access to your OpenAI resource. 

  1. Select the subscription and OpenAI resource to work with. 

  1. Select Manage deployments in your resource and Go to Deployments under Manage your deployments and models. You might first need to scroll down on the landing page. 

  1. Deploy a model using the Deployment APIs. These APIs allow you to specify the model you wish to use. 

  1. Once you create an Azure OpenAI Resource, you must deploy a model before you can start making API calls and generating text. 

 

Get the Secret Key: 

  • Sign into Azure Portal at https://portal.azure.com/ and select Azure OpenAI. 

  • Landing page for cognitive service would be open, select Azure OpenAI > Azure OpenAI. Select the created service. 

  • In overview, click on the Manage Keys > Click here to manage keys. 

  • There would be KEY 1 and KEY 2, you can use either of these. 

 

 
 
Step by Step Integration between Teams and Azure OpenAI 
Integrate Teams request message to virtual agent, communicate with Power Automate flow, communicate with Azure OpenAI using secret key. 

  1. Create a Power Virtual Agent bot in Microsoft Teams. 

  1. Create a Power Automate flow that will be triggered when a message is sent to the bot. 

  1. In the Power Automate flow, use the HTTP action to send a request to Azure OpenAI using the secret key. 

  1. In the Power Automate flow, use the HTTP action to send a response back to the bot. 

  1. Power Virtual Agent bot will response according to the request made in message coming from the teams. 

 

 

Comments

Post a Comment

Popular posts from this blog

🚀 Automatically Moving Business Process Flow (BPF) Stages in Dynamics 365 Using JavaScript

-
Image
In many real-world Dynamics 365 / Model-Driven App implementations, Business Process Flow (BPF) stages must reflect the actual business state of a record , not just user clicks. In this blog, I’ll explain how to automatically move a BPF stage on form load based on: Request Status Assigned To field This ensures the BPF always stays in sync with the record’s lifecycle — even when data is updated by background processes, integrations, or workflows. 🎯 Business Requirement When a record is opened: The BPF stage should automatically move to the correct stage The stage depends on: he_requeststatus he_assignedto Example Rules This removes manual stage movement and improves data accuracy and user experience. 🧠 Key Design Challenges Microsoft does not provide a direct API to jump to a specific BPF stage by name . Instead, we only have: moveNext() movePrevious() So the solution: ✅ Determines the target stage ✅ Figures out whether to move forward ...
Read more

AI-Powered Power Pages Development with Claude Code Plugin

-
  POWER PAGES Plugin for Claude Code A Complete Step-by-Step Guide for Power Platform Consultants ★ Preview Feature   •   Updated March 2026   •   muzairsuleman.blogspot.com   What Is the Power Pages Plugin for Claude Code? If you've ever built a Power Pages site from scratch, you know the drill — scaffolding the project, writing repetitive boilerplate API code, manually configuring Dataverse permissions, and wiring up authentication. It can eat up hours, even for experienced Power Platform consultants.   The Power Pages Plugin for Claude Code flips that experience entirely. Instead of writing code line by line, you describe what you want in plain English inside Claude Code, and the plugin handles the rest — from scaffolding a full single-page application (SPA), setting up Dataverse tables, integrating the Web API, all the way through deploying the site live on Power Pages.   ⚠️   PREVIEW FEATURE This i...
Read more

🛠 Power Automate: Handling Cached Runs After Long Downtime

-
Image
The Challenge If you’ve ever turned off a Power Automate flow for maintenance, debugging, or updates, you may have noticed an unexpected problem when turning it back on: Suddenly, the flow starts running for every single event that happened while it was off. This happens because many connectors in Power Automate cache or store pending events during downtime — so that nothing is lost. While this is a great safeguard in some scenarios, in others it can cause: Outdated notifications being sent after the fact Duplicate processing of already-handled data Overloaded systems with a flood of old runs Confusion for users who receive actions long after they’re relevant Why This Happens When your flow trigger is event-based (e.g., new email, new Dataverse row, SharePoint item created), Power Automate stores those events until your flow is available again. When the flow restarts, it processes all the cached events — effectively “catching up” from when it was last active....
Read more