AI-102 Delivery Completed — Preparing for AI-103: How Is Microsoft AI Training Evolving?
Completed another AI-102 training delivery — and already diving into the roadmap toward AI-103. Recent discussions with learners covered several important areas: - Azure AI Services - Azure OpenAI - RAG patterns & enterprise architectures - Responsible AI - Real-world implementation considerations One thing is becoming increasingly clear: AI capabilities are evolving rapidly, and technical learning paths must evolve just as quickly. For trainers, architects, developers, and organizations, maintaining technical depth while adapting to continuous platform evolution is becoming both a challenge and an opportunity. I'm curious to hear perspectives from the community: What differences or shifts do you expect between AI-102 and AI-103? Which Microsoft AI topics are currently proving most relevant — or most challenging — in your projects?Intelligent Conversations: Building Memory-Driven Bots with Azure AI and Semantic Kernel
Discover how memory-driven AI reshapes the way we interact, learn, and collaborate. 💬✨ On October 20th at 8pm CET, we’ll explore how Semantic Kernel, Azure AI Search, and Azure OpenAI models enable bots that remember context, adapt to users, and deliver truly intelligent conversations. 🤖💭 Join Marko Atanasov and Bojan Ivanovski as they dive into the architecture behind context-aware assistants and the future of personalized learning powered by Azure AI. 🌐💡 ✅ Save your seat on the following link: https://streamyard.com/watch/DN4thzYripaz🚀✨ Are you ready for a power-packed, productive, and inspiring October? ✨🚀
Here we go, friends! 🎉 The October Calendar is officially here, right on time, as always! 🗓️💯 This month, we’re bringing you a lineup of world-class sessions designed to help you: 🌍 Explore the https://www.linkedin.com/company/101186090/admin/page-posts/published/?share=true# ecosystem from new perspectives 💡 Gain practical skills you can apply immediately 🤝 Connect with experts and a global community of learners 🚀 Stay ahead with the latest innovations in Azure, AI, Power Platform, Security, and beyond. What makes this calendar stand out is the incredible diversity of voices and expertise it brings together. 🌍 You’ll hear from global speakers who share not just theory, but real-world experiences across different industries, giving you insights that truly matter. And the best part? ⏰ No matter where you are in the world, the sessions are scheduled across multiple time zones so you can always join in. Even better, everything is completely free and open, because learning and growth should be accessible to everyone. 💙 🔗 Check out the full list of sessions, register today, and prepare yourself for an amazing month of learning, networking, and growth. 🔥 This isn’t just another calendar, it’s your chance to grow, connect, and be inspired alongside thousands of passionate learners across the globe. 🙌 Let’s make October unforgettable together in the https://www.linkedin.com/company/101186090/admin/page-posts/published/?share=true# way! 💙 📢 https://www.linkedin.com/in/kaspersvenmozartjohansen/ 📅 October 4, 2025 06:00 PM CET 📖 Get started with a modern zero trust remote access solution: Microsoft Global Secure Access 🖇️ https://streamyard.com/watch/3APZGyZFRyQS?wt.mc_id=MVP_350258 📢 https://www.linkedin.com/in/akanksha-malik/ 📅 October 7, 2025 19:00 PM AEST 📅 October 7, 2025 10:00 AM CET 📖 Unlocking Document Insights with Azure AI 🖇️ https://streamyard.com/watch/M6qvUYdv58tt?wt.mc_id=MVP_350258 📢 https://www.linkedin.com/in/rexdekoning/ 📅 October 11, 2025 06:00 PM CET 📖 Azure Functions and network security.. Can it be done? 🖇️ https://streamyard.com/watch/RHzXr5bpYHFY?wt.mc_id=MVP_350258 📢 https://www.linkedin.com/in/jeevarajankumar/ 📅 October 7, 2025 18:00 PM AEST 📅 October 19, 2025 09:00 AM CET 📖 D365 Field Service 101 🖇️ https://streamyard.com/watch/RtDkftSxhn7P?wt.mc_id=MVP_350258 📢 https://www.linkedin.com/in/priyankashah/ 📅 October 21, 2025 19:00 PM AEST 📅 October 21, 2025 10:00 AM CET 📖 FSI and Gen AI: Wealth management advisor with Azure Foundry Agents and MCP 🖇️ https://streamyard.com/watch/Vb5rUWMBN9YN?wt.mc_id=MVP_350258 📢 https://www.linkedin.com/in/monaghadiri/ 📅 October 25, 2025 06:00 PM CET 📖 The Role of Sentence Syntax in Security Copilot: Structured Storytelling for Effective Defence 🖇️ https://streamyard.com/watch/EtPkn2EZkauD?wt.mc_id=MVP_350258Unable to locate and add a VM (GPU family) to my available VM options.
I am using azure AI foundry and need to run GPU workload but N-series VM options do not appear when i try to add quota Only CPU families like D and E are listed How can i enable or request N-series GPU VMs in my subscription and regionThe fantastic duo: How to build your modern APIs
🧠 Core Concept The article introduces a Chat Playground System designed to streamline AI development by managing multiple chat scenarios (e.g., technical support, creative writing) from a single dashboard. 🔧 Key Features Scenario-Aware Sessions: Launch pre-configured chat contexts with one click. Dual Access Architecture: FastAPI for RESTful web apps. MCP (Model Context Protocol) for AI tool integration. Streamlit Integration: Wrapped with MCP to allow seamless interaction with AI tools. Automatic Resource Management: Smart port allocation and process cleanup. Context Passing: Uses environment variables and temp JSON files to transfer session data. 🚧 Challenges & Solutions Bridging MCP and Streamlit: Created a wrapper to translate protocol calls and maintain session state. Process Management: Built an async manager to handle multiple Streamlit sessions reliably. Context Transfer: Developed a hybrid system for passing rich context between processes. User Experience: Simplified interface with real-time feedback and intuitive controls. 💡 Lessons Learned Innovation thrives at protocol boundaries. Supporting both REST and MCP broadens adoption. Start simple, scale gradually. Process lifecycle management is critical. Contextual awareness enhances AI utility. Developer experience drives product success. 🔮 Future DirectionsHow to build Tool-calling Agents with Azure OpenAI and Lang Graph
Introducing MyTreat Our demo is a fictional website that shows customers their total bill in dollars, but they have the option of getting the total bill in their local currencies. The button sends a request to the Node.js service and a response is simply returned from our Agent given the tool it chooses. Let’s dive in and understand how this works from a broader perspective. Prerequisites An active Azure subscription. You can sign up for a free trial here or get $100 worth of credits on Azure every year if you are a student. A GitHub account (not necessarily) Node.js LTS 18 + VS Code installed (or your favorite IDE) Basic knowledge of HTML, CSS, JS Creating an Azure OpenAI Resource Go over to your browser and key in portal.azure.com to access the Microsoft Azure Portal. Over there navigate to the search bar and type Azure OpenAI. Go ahead and click on + Create. Fill in the input boxes with appropriate, for example, as shown below then press on next until you reach review and submit then finally click on Create. After the deployment is done, go to the deployment and access Azure AI Foundry portal using the button as show below. You can also use the link as demonstrated below. In the Azure AI Foundry portal, we have to create our model instance so we have to go over to Model Catalog on the left panel beneath Get Started. Select a desired model, in this case I used gpt-35-turbo for chat completion (in your case use gpt-4o). Below is a way of doing this. Choose a model (gpt-4o) Click on deploy Give the deployment a new name e.g. myTreatmodel, then click deploy and wait for it to finish On the left panel go over to deployments and you will see the model you have created. Access your Azure OpenAI Resource Key Go back to Azure portal and specifically to the deployment instance that we have and select on the left panel, Resource Management. Click on Keys and Endpoints. Copy any of the keys as shown below and keep it very safe as we will use it in our .env file. Configuring your project Create a new project folder on your local machine and add these variables to the .env file in the root folder. AZURE_OPENAI_API_INSTANCE_NAME= AZURE_OPENAI_API_DEPLOYMENT_NAME= AZURE_OPENAI_API_KEY= AZURE_OPENAI_API_VERSION="2024-08-01-preview" LANGCHAIN_TRACING_V2="false" LANGCHAIN_CALLBACKS_BACKGROUND = "false" PORT=4556 Starting a new project Go over to https://github.com/tiprock-network/mytreat.git and follow the instructions to setup the new project, if you do not have git installed, go over to the Code button and press Download ZIP. This will enable you get the project folder and follow the same procedure for setting up. Creating a custom tool In the utils folder the math tool was created, this code show below uses tool from Langchain to build a tool and the schema of the tool is created using zod.js, a library that helps in validating an object’s property value. The price function takes in an array of prices and the exchange rate, adds the prices up and converts them using the exchange rate as shown below. import { tool } from '@langchain/core/tools' import { z } from 'zod' const priceConv = tool((input) =>{ //get the prices and add them up after turning each into let sum = 0 input.prices.forEach((price) => { let price_check = parseFloat(price) sum += price_check }) //now change the price using exchange rate let final_price = parseFloat(input.exchange_rate) * sum //return return final_price },{ name: 'add_prices_and_convert', description: 'Add prices and convert based on exchange rate.', schema: z.object({ prices: z.number({ required_error: 'Price should not be empty.', invalid_type_error: 'Price must be a number.' }).array().nonempty().describe('Prices of items listed.'), exchange_rate: z.string().describe('Current currency exchange rate.') }) }) export { priceConv } Utilizing the tool In the controller’s folder we then bring the tool in by importing it. After that we pass it in to our array of tools. Notice that we have the Tavily Search Tool, you can learn how to implement in the Additional Reads Section or just remove it. Agent Model and the Call Process This code defines an AI agent using LangGraph and LangChain.js, powered by GPT-4o from Azure OpenAI. It initializes a ToolNode to manage tools like priceConv and binds them to the agent model. The StateGraph handles decision-making, determining whether the agent should call a tool or return a direct response. If a tool is needed, the workflow routes the request accordingly; otherwise, the agent responds to the user. The callModel function invokes the agent, processing messages and ensuring seamless tool integration. The searchAgentController is a GET endpoint that accepts user queries (text_message). It processes input through the compiled LangGraph workflow, invoking the agent to generate a response. If a tool is required, the agent calls it before finalizing the output. The response is then sent back to the user, ensuring dynamic and efficient tool-assisted reasoning. //create tools the agent will use //const agentTools = [new TavilySearchResults({maxResults:5}), priceConv] const agentTools = [ priceConv] const toolNode = new ToolNode(agentTools) const agentModel = new AzureChatOpenAI({ model:'gpt-4o', temperature:0, azureOpenAIApiKey: AZURE_OPENAI_API_KEY, azureOpenAIApiInstanceName:AZURE_OPENAI_API_INSTANCE_NAME, azureOpenAIApiDeploymentName:AZURE_OPENAI_API_DEPLOYMENT_NAME, azureOpenAIApiVersion:AZURE_OPENAI_API_VERSION }).bindTools(agentTools) //make a decision to continue or not const shouldContinue = ( state ) => { const { messages } = state const lastMessage = messages[messages.length -1] //upon tool call we go to tools if("tool_calls" in lastMessage && Array.isArray(lastMessage.tool_calls) && lastMessage.tool_calls?.length) return "tools"; //if no tool call is made we stop and return back to the user return END } const callModel = async (state) => { const response = await agentModel.invoke(state.messages) return { messages: [response] } } //define a new graph const workflow = new StateGraph(MessagesAnnotation) .addNode("agent", callModel) .addNode("tools", toolNode) .addEdge(START, "agent") .addConditionalEdges("agent", shouldContinue, ["tools", END]) .addEdge("tools", "agent") const appAgent = workflow.compile() The above is implemented with the following code: Frontend The frontend is a simple HTML+CSS+JS stack that demonstrated how you can use an API to integrate this AI Agent to your website. It sends a GET request and uses the response to get back the right answer. Below is an illustration of how fetch API has been used. const searchAgentController = async ( req, res ) => { //get human text const { text_message } = req.query if(!text_message) return res.status(400).json({ message:'No text sent.' }) //invoke the agent const agentFinalState = await appAgent.invoke( { messages: [new HumanMessage(text_message)] }, {streamMode: 'values'} ) //const agentFinalState_b = await agentModel.invoke(text_message) /*return res.status(200).json({ answer:agentFinalState.messages[agentFinalState.messages.length - 1].content })*/ //console.log(agentFinalState_b.tool_calls) res.status(200).json({ text: agentFinalState.messages[agentFinalState.messages.length - 1].content }) } There you go! We have created a basic tool-calling agent using Azure and Langchain successfully, go ahead and expand the code base to your liking. If you have questions you can comment below or reach out on my socials. Additional Reads Azure Open AI Service Models Generative AI for Beginners AI Agents for Beginners Course Lang Graph Tutorial Develop Generative AI Apps in Azure AI Foundry Portal
