Skip to main content

October 2026

Every post published in October 2026, newest first. Pick a day to jump straight to it.

Posts
219
Topics
42
Reading time
29 h
Active days
17

Posts 1–30 of 219 · October 29, 2026

Page 1 of 8

Thursday, October 29, 2026

30 posts

  1. How to Keep Conversation History in a Microsoft Agent Framework AG-UI Server (.NET)

    A Microsoft Agent Framework agent served with MapAGUIServer forgets every message until the server has a session store. Add one with WithInMemorySessionStore for development, continue a thread, see where the history lives, and know the store's limits — with real output from a .NET 10 API.

  2. How to Continue an AG-UI Conversation with threadId and parentRunId

    Send a follow-up to an AG-UI agent that keeps its own sessions: keep the threadId, give the run a new runId, point parentRunId at the previous run and send only the new message — or let the server choose the threadId and read it from RUN_STARTED. Real requests and responses.

  3. How to See the Conversation History Microsoft Foundry Stored for a Response

    Ask Microsoft Foundry which input it used for an answer — the whole conversation, rebuilt from the stored responses — with one az rest command, signed in with Microsoft Entra ID instead of an API key.

  4. How to Run Code Only in Development in ASP.NET Core

    Register a service only on your own machine with builder.Environment.IsDevelopment(), check which environment your app runs in, and test the other branch with dotnet run -e ASPNETCORE_ENVIRONMENT=Production — with real output from a .NET 10 API.

  5. Fixed: AG-UI Agent Receives the Conversation Twice in Microsoft Agent Framework

    A follow-up request that carried the whole chat history made a Microsoft Agent Framework agent read its earlier messages twice, because the server already kept the conversation. Foundry's stored input proved it; sending only the new message fixed it.

  6. Fixed: "Agent Isolation Key Is Required but Was Not Provided by the Configured AgentIsolationKeyProvider"

    Adding WithInMemorySessionStore() to a Microsoft Agent Framework AG-UI agent made every request fail with a 500 and InvalidOperationException: Agent isolation key is required. Here's why the default session store needs to know the caller, and the two ways to fix it.

  7. Fixed: Azure CLI --output table Hides the type Column

    My az rest query asked for type, role and text, but --output table printed only Role and Text. The Azure CLI leaves out keys named id, type and etag in table output; renaming the key in the JMESPath query brings the column back.

  8. Fixed: dotnet run -e Staging Still Starts the App in Development

    I started my ASP.NET Core API with dotnet run -e Staging, and it still logged Hosting environment: Development. The -e option sets an environment variable and needs NAME=VALUE; here are the two commands that really switch the environment.

  9. Fixed: dotnet build Shows the Old "0 Warning(s) 0 Error(s)" Output Instead of Terminal Logger

    dotnet build printed the old console output — Build succeeded, 0 Warning(s), 0 Error(s), Time Elapsed — instead of .NET's Terminal Logger. On macOS and Linux, MSBuild decides from the TERM environment variable, and mine was empty. Here's the check and two fixes.

  10. Build a Career Development Plan App in Power Apps — Part 14: Recap, Production Checklist and Next Steps

    A tour of the finished Career Development Plan app as an employee and a manager, a production checklist for installing, running and updating it, what it doesn't do, ideas for what to build next, and every guide in the series by topic.

  11. Build a Career Development Plan App in Power Apps — Part 13: Install the App in a New Environment

    Install the Career Development Plan release files the way a buyer would: a free trial environment, a group team with Basic User, a new SharePoint site, the Setup solution and its flow, the app with its own site and lists, and a manager and an employee using it.

  12. How to Run User Diagnostics in the Power Platform Admin Center

    Check why someone can or can't use an environment with Run diagnostics: the four access requirements it checks, how to read Results + fixes, and why it says Action needed for people who get their security role from a group team.

  13. How to Add a User to a Power Platform Environment

    Add a person to an environment with a Dataverse database in the Power Platform admin center so they can open its apps: when you need to, the access requirements, the Add user pane, the security role message afterwards, and checking the result.

  14. How to Set Environment Variable Values When Importing a Solution

    When a solution's environment variables have no value, the import asks for one: pick the SharePoint site and lists in the Environment Variables step, or put the values in a deployment settings file with pac solution create-settings for pac solution import.

  15. How to Run an Instant Cloud Flow in Power Automate

    Run a manually triggered cloud flow from its details page, without opening the designer: opening the flow from a solution, the Run button, the Run flow panel's connections and inputs, and checking the run in the 28-day run history.

  16. How to Import a Solution in Power Apps

    Import a managed or unmanaged solution zip into another environment: the Import a solution pane, the details and advanced settings, connections, environment variable values, checking the result, and the same import with pac solution import.

  17. How to Switch Environments in Power Apps

    Move Power Apps to another environment with the environment switcher in the header: the Select environment pane, the Build apps with Dataverse and Other environments groups, and how to check where you are before you create or import anything.

  18. How to Assign a Dataverse Security Role to a Microsoft Entra Group

    Give everyone in a Microsoft Entra security group a Dataverse security role with a group team in the Power Platform admin center: team type, membership type, choosing Basic User, the confirmation that needs its own Save, and how to check the result.

  19. How to Create a Free Trial Environment in Power Platform

    Create a free 30-day trial environment with a Dataverse database in the Power Platform admin center: who can create one, the New environment and Add Dataverse panes, restricting it to a security group, and how long it lasts.

  20. How to Start a Free 30-Day Power Apps Trial

    Start the free 30-day Power Apps trial from Microsoft's trial page: why you need it to create a trial environment even as an admin, the country and terms page, where to check your plan afterwards, and what I saw when the Plan(s) pane didn't change.

  21. Fixed: "You Can't Open Apps in This Environment. You Are Not a Member of the Environment's Security Group" in Power Apps

    A member of the environment's security group got "You can't open apps in this environment" the first time he opened a shared app in a trial environment. Here's what the diagnostics showed, what Microsoft says about trial environments, and how adding people first fixed it.

  22. Fixed: Security Role Isn't Assigned After You Create a Team in the Power Platform Admin Center

    I ticked Basic User while creating a Microsoft Entra group team, selected Save and got a success message, but the team had no role. The role is only assigned after a second Save, in a Role assignment confirmation. Here's how I found it and checked the fix.

  23. Build a Career Development Plan App in Power Apps — Part 12: Run the Solution Checker and Export the Solutions

    Get the Career Development Plan solutions ready to ship: check what each holds, run the solution checker, export version 1.0.0.0 as managed and unmanaged, and take this tenant's SharePoint values out of the app's zips with the Power Platform CLI.

  24. How to Keep Environment Variable Values Out of an Exported Solution

    Remove environment variable current values from exported Power Platform solution zips with the Power Platform CLI: unpack the managed and unmanaged exports together, delete the value files, pack both again and check them, on macOS, Linux or Windows.

  25. How to Export a Solution in Power Apps (Managed or Unmanaged)

    Export a Power Apps solution as a managed and an unmanaged zip with the same version: when to use each, publishing first, setting the version number, downloading the file, and the same export with pac solution export.

  26. How to Run the Solution Checker in Power Apps

    Run the solution checker on an unmanaged solution in Power Apps, read its results and issue details, and run the same check with pac solution check, whose result file names the exact canvas app controls behind each issue.

  27. How to See What's Inside a Power Platform Solution Zip File

    List the files in an exported Power Platform solution zip, read its version and whether it's managed from solution.xml, and find environment variable values before you share it, with commands for macOS, Linux and Windows PowerShell.

  28. How to Sign In to the Power Platform CLI with pac auth create

    Sign the Power Platform CLI in to your tenant with pac auth create and a device code, choose the environment it works with, and check the profile with pac env who and pac auth list, with real output from each command.

  29. Fixed: "No Active Environment Set for the Current Auth Profile" in Power Platform CLI

    The Power Platform CLI signed me in, but the next command failed with No active environment set for the current auth profile. Here's why the new profile had no environment, and the one command that fixed it: pac env select.

  30. Fixed: Environment Variable Export Value Switches Back to Yes in Power Apps

    I set an environment variable's Export value to No and saved, but the panel showed Yes again and the exported solution still held the value. Here's how the zip proved it, what Microsoft's documentation says, and how I took the values out with the Power Platform CLI.