azure / intro-to-intelligent-apps Goto Github PK

In most cases, this lab is run using Codespaces and appears to work well. Some users trying to run the labs using a local instance of Visual Studio code with the devcontainer have experienced some issues. Check the devcontainer setup to make sure it works well for both Codespaces and local VS Code. The experience should be the same.

We looked at adding Azure AD support to the labs for customers that wish to secure access to Azure OpenAI using that method. Whilst possible, it did add a degree of extra unnecessary complexity to the labs. There were also potential issues when using Codespaces with getting AAD auth to work.

To simplify things, this workshop will expect API keys to be used to provide access to the Azure OpenAI service. However, it would be good to add an optional lab which shows how to use Azure AD based authentication, so that participants interested in this method of access control can see how it works.

There are few places, but in labs/03-orchestration/README.md we need to rename it.

Python notebooks work. But .NET ones now require .NET 7, when only .NET 6 is in the dev container.

I have suggested to change:

1. In docker-compose.yml line 13 to "VARIANT: 7.0.jammy"
2. In Dockerfile line 3 tp ARG VARIANT="7.0.jammy"

Works for me.

Would do a pull request if I knew how :-)

Review the prompt engineering exercises to ensure that they're still current and relevant. Update prompt engineering exercises as needed.

Improvement:
Put the excercises into 1 jupyther notebook.
Removes repetitive starting of codespaces python kernels
In case of errors in the .env file you can restart the code in one jupyter file

All required resources described:

• OpenAI (with the right model version)
• Codespaces or Local dev container
• AI Search (with admin key)
• MongoDB on CosmosDB

Currently, the labs use the outdated version 0.17.230711.7-preview of the .NET Semantic Kernel. It should be updated to the latest version.

Running the dev container locally on a Mac with Apple Silicon will fail during the build of the container. The error will be similar to the following:

6.133 E: Unable to locate package azure-functions-core-tools
6.135 ERROR: Feature "Azure Functions Core Tools" (ghcr.io/
[2023-08-15T11:13:12.890Z] jlaundry/devcontainer-features/azure-functions-core-tools) failed to install! Look at the documentation at https://github.com/devcontainers/features/tree/main/src/azure-functions-core-tools for help troubleshooting this error.

This is because there is currently no official release of Azure Functions Core Tools that supports installation inside of a container when running on Apple Silicon:

jlaundry/devcontainer-features#7

Azure/azure-functions-core-tools#3112

The text says, I can't bring my own data into an LLM because the models are pre-trained, so the only way to get more information in is to retrain the model, which is an expensive and time consuming process.

So this statement is contradictory. I can do it, it's just very expensive and resource intensive and time consuming. I suggest to adjust that to avoid confusion.

Remove the Semantic Kernel based example, stick with Langchain.
Add support for Azure Container Apps with Qdrant support.
Deploy full example using azd

For most deliveries of this workshop, customers will likely use a single instance of the Azure OpenAI service for all participants. The .env file should be preconfigured with the correct API key, endpoint etc. values prior to the event. It can then be distributed to participants, which will simplify the setup process and reduce the likelihood of participants not being able to connect to Azure OpenAI to run the labs.

https://github.com/microsoft/chat-copilot

This wont allow Lab 02 - get available model deploys will fail due to inconsistency

Validate that the env var loading works and the user sees that it worked

Can you upadate https://github.com/Azure/intro-to-intelligent-apps/blob/main/presentations/intro-to-intelligent-apps-workshop.pdf please as promised in the OOP2024 WS?

The codespaces / devcontainer setup should allow participants using that method to have a trouble-free experience. For those who wish to fork / clone the repo and run locally, need to provide a detailed list of pre-requisite components that need to be installed.

Merge 03 and 04
Clean up duplicates in Qdrant, Mongo and AI
Move up 05
Delete 06 lab

In the example, we are stating, that the text requires 6 tokens. In reality, it is 7, as the comma , is counted as a separate token.

(Found by one of the participants!)

Create a short video to help participants get up and running with Codespaces prior to the event. This can be distributed a few days before the event to allow people to get Codespaces ready to go.

The env variable name in "labs/03-orchestration/01-Tokens/tokens.ipynb" is called as "AZURE_OPENAI_API_ENDPOINT" but in the .env template it is "AZURE_OPENAI_ENDPOINT".

I think this issue is also present in subsequent files under section 03.