Microsoft .NET 11 Preview 3 Released for Cloud-Native Services and Performance-Sensitive Apps

Microsoft Agent Framework that combines Semantic Kernel and Autogen Frameworks into one, definitely a step in the right direction, still leaves a lot more to be desired. #Microsoft #AgentFramework #AgenticAI

One small change… but a big win for developers. You can now 𝐝𝐨𝐰𝐧𝐥𝐨𝐚𝐝 𝐰𝐫𝐚𝐩𝐩𝐞𝐝 𝐚𝐩𝐩𝐬 𝐝𝐢𝐫𝐞𝐜𝐭𝐥𝐲 𝐟𝐫𝐨𝐦 𝐃𝐚𝐭𝐚𝐯𝐞𝐫𝐬𝐞 , no more dependency on Azure Blob Storage. This means: ✔️ Simpler architecture ✔️ Faster deployment ✔️ Fewer external dependencies ✔️ Better fit for secure environments If you’ve worked with the Wrap feature before, you know the extra steps involved in retrieving binaries. This update removes that friction completely. 👉 Everything stays within Dataverse 👉 Faster build-to-download cycle 👉 Cleaner deployment process Sometimes the most impactful updates aren’t flashy, they just make your daily work easier. #microsoft #PowerApps #PowerPlatform #Dataverse #LowCode #Microsoft #AppDevelopment #DigitalTransformation 📖 I’ve broken it down in detail here: https://lnkd.in/djE6gTES

Key takeaway: Microsoft’s Agent Governance Toolkit gives .NET teams a pragmatic, pluggable way to govern "MCP tool" calls at runtime—so you can enforce policies, capture telemetry, and reduce data- and behavior-related risks from model-driven tool use without invasive changes to your application code. Why this matters for engineering and risk teams: - Centralized control: Apply governance consistently across agents and model tool integrations rather than patching each client. - Policy enforcement at the call level: Block, redact, or transform tool calls to prevent sensitive data leakage or unsafe actions. - Observability and compliance: Capture telemetry and audit trails for tool usage to support investigations and regulatory needs. - Low-friction adoption: The toolkit is designed to be pluggable into .NET applications so governance can be introduced incrementally. If your org is putting models or agents into production—especially those that call external tools—this approach helps bridge developer velocity and operational control. For teams building in .NET, the blog walks through how the Agent Governance Toolkit works and shows patterns for configuring handlers, logging, and policy decisions. Read the Microsoft .NET blog post for implementation details, examples, and guidance on integrating the toolkit into your deployment and compliance workflows. #dotnet #AIgovernance #ResponsibleAI https://lnkd.in/ePe4SJHV

Microsoft Releases .NET 11 Preview 3 with Updates Across Runtime, SDK, MAUI, and ASP.NET C. Developer platform shifts like this often matter before they look dramatic in the market. What happened: Microsoft has released. NET 11 Preview 3, the third preview of its upcoming Standard Term Support version due in November 2026. Why it matters: This directly affects developer workflows, framework adoption, or release execution for engineering teams. That makes it relevant well beyond the headline feature itself. Strategic takeaway: The bigger signal is that advantage in the. NET ecosystem is increasingly shaped by lower workflow friction, better tooling, and faster delivery loops. Source: InfoQ .NET Original article: https://lnkd.in/dzXRmDbH Curated by AI News Curator.

What matters is not the preview feature. What matters is the friction it removes. Fabric Lakehouse auto-binding in Git looks small on the surface, but in practice these are the changes that improve enterprise delivery. In my experience, teams rarely get stuck because a platform lacks another big feature. They get stuck because manual rebinding, environment drift, and awkward handoffs keep slowing the work down. That is why I think this matters. If Microsoft keeps reducing friction between source control, notebooks, and core data assets, Fabric becomes easier to govern, easier to standardise, and easier to trust as an operating model. The practical takeaway is simple: simplification is not cosmetic. It is part of reliability, adoption, and scale. #MicrosoftFabric #DataOps What small platform change has made the biggest difference to adoption or reliability in your team?

Your competitor shipped last quarter. You're still debating folder structure. That's not a people problem. That's a build-stage problem. And it kills more software products than bad ideas ever will. Microsoft's Quick-Start Development Toolkit in App Advisor was built for exactly this moment – deployable code templates, proven Azure reference architectures, and a guided wizard that routes your team to the right build pattern before the first standup ends. AI agents, AWS-to-Microsoft Azure migrations, security-first integrations – pick your scenario, skip the setup spiral, and ship. Concept to prototype. Without the six-week detour. Flexsin Inc. has been in this exact room with engineering teams for 17 years – the room where good ideas either get architecture and momentum, or quietly disappear. As a certified Microsoft Partner, we've built the playbooks, the pipelines, and the Marketplace-ready products to prove it. The toolkit is ready. Here’s how we actually help teams go from idea to shipped product. https://lnkd.in/g73nAQZ5 https://lnkd.in/gEzxQHkK #MicrosoftMarketplace #AzureDevelopment #AppAdvisor #AIAgents #MicrosoftPartner #ISV #CloudNative

🚀 Microsoft Just Dropped a Bombshell for Devs: .NET 11 & The Era of AI Agents If you’ve been waiting for the "next big thing" in development, the April 2026 Microsoft Dev Blog updates just delivered it. We are officially moving past AI "prototypes" and into the era of Scalable AI Agents. I’ve been diving into the latest technical releases, and three things stand out that will change how we build this year: 1. .NET 11 Preview 3: The Performance Beast ⚡ Microsoft is doubling down on "Inner Loop" productivity. JIT Optimizations: Significant improvements to switches and bounds checks mean your high-scale apps just got a "free" speed boost. dotnet watch: New crash recovery and Windows desktop improvements are making the developer experience smoother than ever. 2. The New "Azure AI Apps and Agents Developer" Certification (AI-103) 🤖 This is a clear signal from Redmond: Agentic AI is the new standard. Microsoft has launched a new certification focused on building production-ready agents using Azure AI Foundry. It’s no longer about just "chatting" with an LLM; it’s about building autonomous, multi-modal workflows that actually execute business logic. 3. Foundry Toolkit for VS Code is now GA 🛠️ The "Foundry Toolkit" reaching General Availability is a game-changer for those of us focused on AI automation. It allows you to build, test, and deploy AI agents directly from VS Code with enterprise-grade governance. The barrier between "Idea" and "Autonomous Agent" is disappearing. If you aren't looking at how to integrate agentic workflows into your stack, you're building for 2024, not 2026. Are you planning to take the new AI-103 exam, or are you focusing on the .NET 11 performance upgrades first? Let’s talk strategy in the comments! 👇 #MicrosoftDev #DotNet11 #AIAgents #AzureAI #SoftwareEngineering #DeveloperExperience #CloudComputing #AI103 #AgenticAI #WebDev

What is Microsoft Graph API and why it matters in Automation? A recent requirement around OTP and email handling pushed me to explore Microsoft Graph API more deeply and it is something every automation engineer should know. What is Graph API -A unified REST API from Microsoft -Gives access to Outlook emails, Azure AD, Teams, OneDrive and more -Works through a single endpoint graph.microsoft.com Where to use it in automation: -Fetch OTP from mailbox for email-based authentication -Validate emails and notifications -Manage test users in Azure AD -Read attachments or reports Key takeaway: Graph API helps shift from UI-driven automation to service-level automation which is faster more stable and scalable. #Java #Automation #MicrosoftGraph #Azure #SDET #DevOps

.NET 10 just dropped hundreds of performance improvements — and most of them are completely free. No major refactoring. No breaking changes. Just upgrade and watch your app get faster. Here’s what stood out to me after going through the official Microsoft benchmarks: Blazor’s core script went from 183 KB down to 43 KB. That’s a 76% reduction — with automatic Brotli/gzip compression and fingerprinting built in. On mobile or slower networks, that difference is night and day for first impressions. HttpClient response streaming is now on by default. Previously opt-in, it now uses BrowserHttpReadStream instead of MemoryStream — which means lower memory usage and noticeably better handling of large payloads. Minimal APIs finally have built-in validation via AddValidation(). No more reaching for FluentValidation just to cover the basics. DataAnnotations and custom rules work out of the box. Server-Sent Events are now a single line with TypedResults.ServerSentEvents(). If you only need one-way real-time push, this is significantly lighter than pulling in SignalR. And under the hood? URI parsing is ~88% faster, JSON serialization is ~33% faster with near-zero allocations in some paths, and the JIT inlining budget has been doubled. Stack allocations in hot paths mean your GC is doing a lot less work. These aren’t synthetic benchmarks — these are measured improvements from Stephen Toub’s official .NET 10 performance blog. If you’re on .NET 8 or 9, the upgrade path is straightforward. The gains are real. Have you migrated yet? Curious what performance difference you’ve seen — drop it in the comments 👇 #DotNet10 #ASPNETCore #Blazor #CSharp #Performance #WebDevelopment