Overview

As organizations begin adopting autonomous agents through Microsoft Copilot, Agent 365, and Copilot Studio, a new challenge emerges: where do those agents actually perform work? While modern AI models are excellent at reasoning, planning, and orchestrating tasks, many business processes still require interacting with applications, websites, files, and systems that were designed for humans. This is where Windows 365 for Agents comes into play.

Windows 365 for Agents introduces a new class of Cloud PCs designed specifically for AI agents. Built on the same Windows 365 platform used by Windows 365 Enterprise and Business, it provides agents with secure, scalable Windows environments where they can perform real work. Agents can launch applications, navigate web pages, manipulate files, interact with legacy systems, and execute tasks that may not have modern APIs available. This allows organizations to expand agent capabilities far beyond simple API-based automation while maintaining enterprise security, governance, and compliance controls.

How Windows 365 for Agents Works

Read More

Overview

AI agents are quickly evolving from isolated experiments into digital workers that can access data, invoke tools, automate processes, and collaborate with employees. As the number of agents grows, organizations need a consistent way to understand which agents exist, what resources they can access, and how their activities are governed.

Microsoft Agent 365 provides a unified control plane for observing, governing, and securing AI agents across the enterprise. It is designed to support agents built with Microsoft platforms such as Microsoft Foundry and Copilot Studio, as well as agents from third-party platforms and partner ecosystems. This gives IT and security teams a centralized way to manage agents regardless of where they were created.

How Microsoft Agent 365 Works

Read More

Overview

As Microsoft Fabric environments mature and become more collaborative, the risk of accidental deletion increases. A data engineer cleaning up a workspace, an analyst removing unused assets, or a contributor misunderstanding dependencies can easily delete the wrong item. Until recently, that deletion was permanent.

Microsoft Fabric now introduces item-level recovery through soft delete, providing a critical safety net for supported Fabric items. This capability complements existing workspace retention and adds fine-grained protection at the item level.

Item recovery allows deleted items to be retained for a configurable period, during which authorized users can restore them or permanently delete them. This feature is currently available in preview and must be explicitly enabled at the tenant level.

Prerequisites and Configuration

Read More

Overview

At FabCon 2026, Microsoft took another important step toward reshaping how organizations manage databases by announcing the Database Hub in Microsoft Fabric. While the Database Hub is still in early access and not yet generally available, it represents a meaningful shift in how Microsoft is thinking about database management at scale.

For years, database teams have operated across fragmented tools, portals, and management experiences depending on whether the database lived on‑premises, in Azure PaaS, or in a SaaS environment. As data estates grow and AI workloads place greater pressure on operational data, that fragmentation becomes a real problem. The Database Hub is Microsoft’s answer to this challenge, providing a unified control plane for managing databases across the enterprise from within Fabric.

Anyone running SQL Server today, whether on‑premises or in Azure, should be paying close attention. This is not just another management experience. It is a signal of where Microsoft is taking databases as part of a single, converged data platform.

What the Database Hub Is

Read More

Overview

Microsoft Fabric security is built on two distinct layers that are often confused but serve very different purposes:

• Control plane access determines what you can do in Fabric, such as creating items, managing workspaces, and sharing content.
• Data plane access determines what data you can actually see or interact with inside OneLake.

For much of Fabric’s early life, workspace roles were used as the primary security boundary. That works for collaboration, but it becomes problematic as platforms scale and data products need stronger governance.

This is where OneLake security comes in. It introduces native, fine-grained security directly at the storage layer, allowing organizations to separate operational permissions from data access. At FabCon, Microsoft announced that OneLake security is going GA in April 2026, signaling that this model is ready to become the standard for enterprise Fabric deployments.

Control Plane Access: Workspace Roles

Read More

Overview

Microsoft Fabric provides multiple ways to implement transformation logic and operationalize it within Fabric Data Factory pipelines. Two of the most common approaches are Fabric notebooks and SQL stored procedures.

Both are first class tools in Fabric and both can be orchestrated through Data Factory pipelines. The difference is not about which one is better. It is about how the processing is executed, where the logic lives, and what development style best fits the workload.

Notebooks are built on Apache Spark and are designed for distributed, code driven data engineering and analytics workflows. Stored procedures run directly in the SQL engine and are optimized for relational, database centric operations. In real world Fabric architectures, it is common and often recommended to use both together.

Understanding the strengths of each helps teams design pipelines that are scalable, maintainable, and aligned with how their data is structured and governed.

Fabric Notebooks

Read More

Overview

A data gateway in Microsoft Fabric and Power BI is the secure connectivity layer that allows cloud services to access data sources that aren’t publicly reachable. This includes on-premises systems, Azure resources locked behind private endpoints, and streaming platforms running inside private networks.

Gateways are critical because most real-world architectures are hybrid. Even as organizations adopt Fabric, they often need to integrate with legacy systems, tightly secured Azure services, or real-time platforms that cannot be exposed to the public internet. Gateways make this possible without compromising security or network boundaries.

Microsoft Fabric currently supports three gateway types, each optimized for a different scenario:

• On-premises data gateway
• Virtual network data gateway
• Streaming virtual network data gateway

Understanding when to use each one helps avoid unnecessary complexity and ensures the right balance of security, performance, and manageability.

What a Data Gateway Does in Fabric and Power BI

Read More

Overview

Organizations building modern analytics platforms on Azure often start with Azure Data Lake Storage Gen2 as their foundational storage layer. Azure Data Lake is highly scalable, cost effective, and flexible, making it an attractive landing zone for raw data of all types. However, without strong governance, modeling, and processing layers, many data lakes gradually devolve into what is commonly referred to as a data swamp.

Microsoft Fabric Lakehouse was introduced to address these challenges by combining the openness of a data lake with the structure, governance, and usability of a warehouse. Unlike a traditional data lake, Fabric Lakehouse is delivered as a fully managed SaaS experience that tightly integrates storage, compute, governance, security, and analytics into a single platform.

Understanding the differences between Azure Data Lake and Fabric Lakehouse is critical when designing scalable, maintainable, and business-ready data architectures.

Azure Data Lake Storage Gen2

Read More

Overview

Microsoft operates multiple Azure cloud environments to support a wide range of regulatory, security, and compliance needs. Two of the most important, and most commonly misunderstood, are Azure Commercial (Public) and Azure Government. While both environments are built on the same underlying Azure technology stack, they are designed for fundamentally different use cases, particularly when paired with Microsoft 365 offerings such as Commercial, GCC, GCC High, and DoD.

Azure Commercial, also referred to as global or public Azure, is Microsoft’s standard cloud platform used by enterprises worldwide. It offers the broadest service catalog, the fastest access to new features, and global regional availability. Both Microsoft 365 Commercial tenants and GCC (Government Community Cloud – Moderate) tenants rely on Azure Commercial as their underlying Azure platform.

Azure Government, by contrast, is a separate, sovereign cloud built exclusively for U.S. government agencies and their authorized partners. It operates in physically isolated U.S. datacenters, is managed by screened U.S. persons, and is authorized for high‑impact government workloads. This separation is not merely contractual or logical; it is enforced across the infrastructure, network, and identity layers.

Because of these enforced boundaries, Azure Government is the required Azure platform for organizations using Microsoft 365 GCC High or Microsoft 365 DoD. Both of these Microsoft 365 environments are paired with Microsoft Entra ID in Azure Government, ensuring identity, data residency, and access controls remain within the same sovereign cloud boundary.

Comparison: Azure Commercial vs Azure Government

Read More

Read More