A sample application showing a secure setup with
- Azure Open AI
- Bot Composer Bot using Managed Identity
- Document Cracking function
- Vector search
- Open AI function calling
azd init -t graemefoster/LockedDownChatBotTo use a different location (eastus default) for a new OpenAI service
azd env set OPENAI_LOCATION <open-ai-location>When you're ready to deploy:
azd up- Use GPT3.5-Turbo >= 0613. This model has been trained on functions (see here)
- The function support is very loose.. The prompt appears pretty stable now, but I still see GPT get excited and add natural language every now and again!
- MS API doesn't support function calling via its API, but (this[https://codeconfessions.substack.com/p/creating-chatgpt-plugins-using-the]) looks useful
- Bot Composer custom dialogues are really useful, but won't work in Power Virtual Assistants. However you could use a custom skill / logic app / external
As of July 2023 the Azure Open AI support is maturing, but it still missing a few features to enable some experiences:
We are seeing maturing of Azure Open AI through features like Bring Your Own Data. But as of July 2023, these do not enable you to make private network calls to your Data Sources.
The current approach is to use Public accessible Data Sources.
PVA support for Bots is maturing rapidly. But your options for accessing secure data involve deploying Power Data Gateways to your on-premises networks. This can be tricky for organisations with strict Security Zone models, who wish to enhance Bot experiences with secure data.
Azure OpenAI does not support 'Functions' where you can explicitly ask OpenAI to comprehend an utterance, and output a very specific format response.
This repository provides templates and code to address each of the above capabilities.
The sample runs a Bot Composer Bot inside your own network, where it can be zoned appropriately to access the data it requires.
The sample sets up a Teams Channel which connects to your Bot via the Application Gateway
Not 100%, but the sample shows some System Prompts that can get JSON output to assist with you calling Downstream APIs.
The solution can run within an Azure Architecture like this with Firewalls and Gateways at the edge. Firewall and Gateway are not part of the default deployment of this template.
