Pure Virtual C++ is back! For the 7th year running, we’re hosting a free, one-day virtual conference for the whole C++ community. Whether you joined us back in 2020 when we first launched or you’re discovering the event for the first time, we’d love to have you.

Mark your calendar: Tuesday, July 21, 2026, starting at 16:00 UTC (9:00 AM in Seattle/Los Angeles, 1:00 PM in Buenos Aires, 12:00 AM in Hong Kong). The conference runs approximately 2 hours and will be streamed live on both YouTube and Twitch, so you can watch from anywhere in the world.

The full speaker lineup and detailed schedule will be announced in follow-up posts — stay tuned.

The conference is completely free. Register here to save your spot and get notified when the schedule goes live. Can’t make it live? All sessions will be available on-demand on the Visual Studio YouTube channel after the event.

Great news! Registration is officially open to Microsoft Ignite 2026. Secure your spot at Microsoft’s flagship event of the year.

At Microsoft Ignite, you’ll discover the latest innovations, practical insights, and build skills you can apply immediately. Join business and IT professionals, developers, and partners to explore important announcements and learn from real-world implementations.

Hear directly from Microsoft leaders shaping the future of cloud and AI:

  • Arun Ulag, Executive Vice President, Azure Data, Microsoft
  • Nicole Herskowitz, CVP, Microsoft 365 and Copilot
  • Omar Shahine, CVP, Microsoft Scout
  • Bryan Goode, CVP, Business Applications
  • Vasu Jakkal, CVP, Marketing Security
  • Jared Spataro, CMO, AI at Work
  • Mark Russinovich, CTO, Deputy CISO, and Technical Fellow, Microsoft Azure
  • Cyril Belikoff, Vice President Cloud and AI
  • Nitasha Chopra, Vice President and Chief Operating Officer, Copilot Studio
  • Seth Juarez, Staff Developer Advocate

From expert-led sessions and hands-on learning to immersive Hub experiences and valuable community connections, Microsoft Ignite is designed to help you turn discovery into action and move forward with confidence.

Space is limited, so register today:
https://ignite.microsoft.com/en-US/home

Time to change the way you build your Power Apps Canvas Apps. Low-code development can no longer be the Wild West.

  • Drag & drop apps thrown together without structure just don’t cut it anymore.
  • Development without architecture leads to technical debt, inconsistency, and maintenance nightmares.
  • And the worst part? The hidden waste in your apps.
    • Duplicated logic
    • Repeated controls
    • Poorly managed state

The result? Apps that are hard to maintain, slow to evolve, and frustrating to adapt to growing complexity.

That’s exactly why Nicolo Ferranti, Microsoft Power Platform MVP, wrote this new, free guide:

  • User Defined Functions (UDFs) and User Defined Types (UDTs)
    → to write cleaner, reusable, and more maintainable code
  • Centralised state management
    → for clear, predictable app behaviour
  • A structured architectural approach
    → to prevent chaos before it starts

If you’re building with Power Apps and ready to move beyond copy-paste development, this guide is for you. This guide aims to demonstrate how these new features can help you build Power Apps Canvas applications with greater accuracy and architectural discipline.

Download the full eBook by Microsoft Power Platform MVP, Nicolo Ferranti, here:

The National Health Service of England is rolling out Microsoft 365 Copilot to 505,000 clinicians & support staff.

More than half a million NHS staff are being given access to new artificial intelligence (AI) tools that could free up an average of 2 days every month from admin duties, freeing up more time for the duties that matter most for patients and staff.

NHS England announced today that it is significantly accelerating AI adoption across healthcare services by providing 505,000 clinicians and support staff with access to Microsoft 365 Copilot.

The AI personal assistant helps clinicians to draft documents and analyse data more efficiently to focus more time on patient care.

The agreement follows the largest AI trial of its kind globally in healthcare, which provided more than 30,000 NHS workers across 90 NHS organisations with access to Microsoft 365 Copilot.

It found that AI-powered administrative support could save an average of 43 minutes per staff member per day or more, which equates to 5 weeks of time per person annually.

Results from the trial showed that a full rollout of Microsoft 365 Copilot could save millions of hours of staff time per month.

For more, visit:

KPMG and Microsoft are expanding their partnership to help clients manage, monitor and securely deploy AI at scale across their own organisations with Agent 365 and Copilot. At the same time, KPMG’s member firms will roll out Microsoft 365 Copilot to 276,000 employees worldwide.

The expansion is the latest move to embed Microsoft technology into KPMG’s global client service delivery platforms and enable organisations to monitor, govern and control AI agents from a central location. The deal enables KPMG to use Microsoft Agent 365 to enhance how services are delivered in its audit, tax and advisory services, including smart audit platform KPMG Clara, while helping clients build agent-powered operating models to securely deploy AI agents across their own organisations. 

Read more here:

Brad Smith, Microsoft’s President, recently had a post to technology leaders about the message students are sending to those in the AI industry:

“This year’s graduates are sending a clear message about AI and jobs. We should listen. They’re reminding us that AI should serve people, not replace them. Microsoft’s mission is to empower every person and organization to achieve more. That means helping people build the skills to use technology to create new opportunities. If we’re not doing that, we’re not doing our job.”

He expands on our company’s sentiment at “Microsoft On The Issues“. For obvious reasons, this is a very important article to our community & our company & will help people understanding our philosophy & values around AI, people & technology’s place in the future.

I would add a second message for today’s graduates: you’re in a unique position to have a positive impact. You’ve lived through significant challenges. While it may feel unfair that the job market is so uncertain, you were made for this moment. Technology is second nature to your generation. Constant change has taught you how to adapt quickly. As AI reshapes how we work, you don’t need to unlearn decades of habits the way some of us do. You are better equipped to move forward.   

Technology will change, but you can stand firmly and speak loudly for values that are timeless. Agency. Ambition. Dignity. All fulfilled through work and technology that gives us purpose.  

Do everything you can to help advance these values.

Read his post here:

Posted by: kurtsh | June 3, 2026

EVENT: Microsoft Build 2026 – Live Blog!

All the announcements from the keynote are summarized on the Build 2026 Live Blog which has short synopses of each event. I highly encourage taking a look at the live blog because frankly, it can be overwhelming – the amount of information that was announced!

Here’s shortcuts to the full overviews of each:

If you watch Satya Nadella’s Build 2026 keynote in it’s entirety, here’s a list of all the shortcuts they posted in the video:
(I’ll put descriptions of each later but I wanted to get these into the post before I forget)

At Microsoft Build 2026, we announced the public preview of Azure Linux 4.0 – Microsoft’s first party Linux distribution, purpose-built for Azure. Azure Linux 4.0 is available now for Azure Virtual Machines, VM Scale Sets, and container images – with Azure Kubernetes Service (AKS) support and Windows Subsystem for Linux (WSL) coming soon after.

Why Azure Linux 

Running Linux on Azure often involves a mix of distributions – one for VMs, another for Kubernetes nodes, a third for container base images, and sometimes something different on developer machines. That flexibility is powerful, but it can also introduce operational overhead: multiple patch schedules to coordinate, multiple security baselines to validate, and more moving parts for SRE and security teams to stay ahead of. A more consistent baseline – especially one with a smaller footprint – can help reduce exposure and simplify day‑to‑day maintenance 

Azure Linux was built with that principle in mind: a single, Microsoft-supported Linux foundation designed to work across every Azure compute surface. From kernel updates to CVE patches, Azure Linux is built and maintained by Microsoft with a predictable update cadence designed around Azure infrastructure. Azure Linux is included with Azure compute at no additional cost. 

What Is Azure Linux 4.0 

Azure Linux is a Fedora-derived, RPM-based Linux distribution built and maintained by Microsoft. It is open source, free to use, and optimized specifically for Azure. Minimal by choice, secure by default; Azure Linux ships only the packages required for cloud workloads. Azure Linux is built exclusively for cloud and server workloads, it is not intended to support desktop usage or GUI applications.  

Azure Linux already powers millions of cores across Azure’s internal services, including AKS, Azure SQL, Azure Cosmos DB, and many others. With 4.0, we’re bringing the same OS – same security posture, same performance tuning, same operational simplicity – to every Azure customer. 

When Azure Linux 4.0 reaches General Availability, you can expect seamless integration with the Azure services you already rely on, including: 

  • Microsoft Defender for Cloud – vulnerability assessment and threat detection 
  • Azure Monitor – telemetry, logs, and performance monitoring 
  • Azure Migrate – discovery and migration tooling 
  • Trusted Launch and Secure Boot – hardware-rooted security 
  • Azure Portal, CLI, ARM, Bicep, Terraform, Ansible -deploy and manage with your existing tools 

Read more at:

<taken from Microsoft 365 Message Center (GCC MC1262588, Commercial MC1262588: “Microsoft Teams: Retirement of CAPTCHA for meeting join”, published Mar 26, 2026>

Introduction

Microsoft Teams is retiring CAPTCHA for meeting join to improve accessibility, reduce join friction, and modernize protections against automated participants. This change follows the release of a new, default‑on capability that detects external meeting assistant bots and provides organizers with increased visibility and control during the meeting join process, as previously announced in Message Center post MC1251206 (Microsoft 365 Roadmap ID 558107).

To ensure a smooth transition:

  • The new bot detection capability will be released and available to customers before CAPTCHA deprecation occurs.
  • There will be no gap where meetings are left without baseline bot protection.
  • CAPTCHA will be removed from meeting join flows and admin surfaces only after the new capability is fully in place.

When this will happen

  • Early May 2026: The Require verification by participants (CAPTCHA) policy will be locked and can no longer be enabled.
  • Late July 2026: CAPTCHA policy removed from PowerShell.
  • Late August 2026: CAPTCHA policy removed from the Teams Admin Center UI.

Note: Dates are subject to change based on the release of bot identification (MC1251206/Roadmap ID 558107). 

How this affects your organization

Who is affected

  • Microsoft Teams tenant administrators
  • Meeting organizers with anonymous or external participants

What will happen

  • The CAPTCHA meeting policy will be retired and removed.
  • CAPTCHA challenges will no longer appear during meeting join.
  • A new, default‑on bot detection capability will provide baseline protection.
  • Detected bots will require organizer approval to join meetings (recommended default).
  • There will be no gap in bot protection during the transition.

What you can do to prepare

  • No immediate action is required.
  • Review the new meeting policy when it becomes available in the Teams Admin Center.
  • Keep the default setting that requires organizer approval for detected bots.
  • Update internal documentation or helpdesk guidance related to meeting join and lobby controls.

Compliance considerations

  • Admin control introduced: A new meeting policy governs how detected external bots are handled during meeting join.

<taken from Microsoft 365 Message Center MC1251206: “Microsoft Teams: Identify external bots joining your Teams meetings” Published Mar 13, 2026>

AI‑powered meeting assistant bots—such as transcription and summarization services—are increasingly used to enhance productivity in online meetings. While these tools can be valuable, some bots may access meetings without the knowledge or consent of the meeting organizer or the hosting tenant, which can create data security, privacy, and compliance risks.

To help organizations protect meeting content and increase visibility into automated participants, Microsoft Teams is introducing a new capability that detects external meeting assistant bots as they attempt to join meetings. This update gives organizers greater awareness and control and provides administrators with clear controls to manage how detected bots are handled in meetings hosted across the organization.

This message is associated with Microsoft 365 Roadmap ID 558107.

When this will happen

How this will affect your organization

Who is affected

  • All organizations using Microsoft Teams meetings, including GCC tenants
  • Meeting organizers and Teams administrators

What will happen

  • Teams will detect external meeting bots as they attempt to join meetings hosted by your organization.
  • When detected, bots will be clearly labeled in the meeting lobby experience.
    • Note: There might still be bots that are undetected by the system due to their intrinsic behavior. Please inform your users to report them out directly from the app/meeting. This will help us improve our detection system.
  • Organizers will be able to:
    • approve or deny detected bots from the meeting lobby.
    • see clearly which participants have been identified as bots.
    • remove detected bots during the meeting if necessary.
  • These organizer controls are designed to help ensure that bot participation in meetings is an intentional and informed decision.
  • A new meeting policy will be available in the Teams admin center that allows admins to configure how detected bots are handled (do not detect bots, require approval). In the future, we intend to provide more granular controls to admins, as appropriate.
  • Bot detection will be enabled by default for all tenants.
  • Teams will continue improving detection accuracy; however, some bots may not be detected in all scenarios.

What you can do to prepare
No action is required at this time.

However, we recommend that Teams admins:

  • Review the new meeting policy in the Teams admin center once it becomes available.
  • Keep the default setting, which requires organizers to approve detected bots before they join meetings (recommended).
  • Choose a stricter or more permissive option based on your organization’s collaboration and compliance requirements.
  • Inform meeting organizers that they may see new indicators and approval prompts when detected bots attempt to join meetings.
  • Update internal helpdesk or governance documentation if your organization documents meeting join or lobby controls behavior.
  • Monitor future Message center updates for expanded administrative controls.

Compliance considerations

QuestionAnswer
Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to your data?Yes. This change introduces detection logic that analyzes meeting join metadata to identify external automated bots attempting to join meetings.
Does the change provide a new way of communicating between users, tenants, or subscriptions?No. The feature only changes how external meeting assistant bots are surfaced to organizers during the meeting join process, increasing visibility of automated external participants. There is no change in the way participants can communicate with these bots or vice versa.
Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. The change introduces a new meeting policy in the Teams admin center that allows admins to define how detected bots are handled. It cannot be controlled through Entra ID group membership at this time.

Older Posts »

Categories