<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Healthcare and Life Sciences Blog articles</title>
    <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/bg-p/HealthcareAndLifeSciencesBlog</link>
    <description>Healthcare and Life Sciences Blog articles</description>
    <pubDate>Fri, 13 Nov 2026 13:35:56 GMT</pubDate>
    <dc:creator>HealthcareAndLifeSciencesBlog</dc:creator>
    <dc:date>2026-11-13T13:35:56Z</dc:date>
    <item>
      <title>Building Private Connectivity for Fabric workloads</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/building-private-connectivity-for-fabric-workloads/ba-p/4572657</link>
      <description>&lt;P&gt;As part of our&amp;nbsp;&lt;STRONG&gt;Amplify Healthcare Intelligence&lt;/STRONG&gt; webinar and workshop series, we hosted a session exploring how to securely connect Microsoft Fabric and Power BI to on-premises SQL Server using private connectivity.&lt;/P&gt;
&lt;P&gt;Led by &lt;SPAN data-wra="1"&gt;&lt;A href="https://www.linkedin.com/in/girishkpillai/" data-tabster="{&amp;quot;restorer&amp;quot;:{&amp;quot;type&amp;quot;:1}}" target="_blank"&gt;Girish Pillai&lt;/A&gt;&lt;/SPAN&gt;, the session covered the essential building blocks for hybrid data connectivity, including VNet data gateways, on-premises data gateways, and managed private endpoints with Private Link Service.&lt;/P&gt;
&lt;P&gt;The presentation walks through four reference architectures:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;VNet data gateway over ExpressRoute&lt;/LI&gt;
&lt;LI&gt;VNet data gateway over Site-to-Site VPN&lt;/LI&gt;
&lt;LI&gt;Outbound-only on-premises data gateway&lt;/LI&gt;
&lt;LI&gt;Managed private endpoint for Fabric Spark workloads&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Each architecture addresses connectivity and routing, gateway configuration and identity, DNS, data protection, and considerations for choosing the right approach.&lt;/P&gt;
&lt;P&gt;The deck also includes a side-by-side comparison to help you evaluate these options based on workload requirements, operational ownership, and bandwidth considerations.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Download the presentation below&lt;/STRONG&gt; to use as a reference when planning your own secure, AI-ready healthcare data architecture. Be sure to check out the final slides for upcoming sessions in the Amplify Healthcare Intelligence series.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Nov 2026 21:29:16 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/building-private-connectivity-for-fabric-workloads/ba-p/4572657</guid>
      <dc:creator>MatthewAnderson</dc:creator>
      <dc:date>2026-11-11T21:29:16Z</dc:date>
    </item>
    <item>
      <title>Securing the Non-Human Identity Attack Surface</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/securing-the-non-human-identity-attack-surface/ba-p/4571497</link>
      <description>&lt;P&gt;Cybersecurity teams often spend most of their efforts on securing and governing human identities: enforcing Multi-Factor Authentication (MFA), monitoring phishing campaigns, and tightening joiner-mover-leaver processes.&lt;/P&gt;
&lt;P&gt;Yet, lurking quietly inside every information technology environment is an entirely different population that frequently outnumbers employees: Non-Human Identities (NHI).&lt;/P&gt;
&lt;P&gt;These workload identities—which encompass &lt;STRONG&gt;applications, service principals, managed identities, CI/CD runners, and automated AI agents&lt;/STRONG&gt;—are the connective tissue powering modern IT operations. They run deployment pipelines, automate resource provisioning, and pull data from cloud APIs.&lt;/P&gt;
&lt;img /&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Unlike human users, however,&amp;nbsp;&lt;STRONG&gt;they cannot complete an MFA prompt&lt;/STRONG&gt;. When an attacker gets their hands on a service principal’s credentials, there is no push notification or phone call standing in the way.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;img /&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;The Core Problem&lt;/U&gt;&lt;/STRONG&gt;&lt;STRONG&gt;: Security &amp;amp; Governance Asymmetry&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Organizations routinely hold human users to rigorous security standards while letting NHIs operate with sprawling, unmonitored privileges.&lt;/P&gt;
&lt;P&gt;This disparity turns machine accounts into a high-value attack surface. Once compromised, an identity with broad infrastructure and application permissions grants immediate, high-speed execution capabilities.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;img /&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With AI agents proliferating, automated attacks are evolving. In late 2026, Microsoft published threat intelligence on “&lt;STRONG&gt;&lt;EM&gt;Storm-3168: Agentic-driven cloud attacks using compromised service principals”&lt;/EM&gt; &lt;A href="https://www.microsoft.com/en-us/security/blog/2026/09/25/storm-3168-agentic-driven-cloud-attacks-using-compromised-service-principals/" target="_blank" rel="noopener"&gt;[1]&lt;/A&gt;&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;The immediate danger isn't a science-fiction swarm of sentient rogue AIs. Rather, it is &lt;STRONG&gt;machine-speed execution&lt;/STRONG&gt;: scripts and agents performing rapid credential stuffing, instant permission discovery, and automated API reconnaissance through identities that bypass human friction.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;img /&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;SPAN class="lia-text-color-15"&gt;These modern threats need a modern and comprehensive solution for advanced cyber warfare.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;H5&gt;&lt;STRONG&gt;&lt;U&gt;The Solution&lt;/U&gt;: &lt;EM&gt;Microsoft’s multi-layer defense mode: Entra Workload ID Premium + Defender for Cloud (Defender for Resource Manager) + Agent 365&lt;/EM&gt;&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;Defending NHIs requires stopping unauthorized access at authentication &lt;STRONG&gt;and&lt;/STRONG&gt; monitoring what the identity does once inside. Microsoft tackles this through a multi-layer defense strategy.&lt;/P&gt;
&lt;H5&gt;Layer 1 | Control the Front Door with Microsoft Entra Workload ID&lt;/H5&gt;
&lt;P&gt;Microsoft Entra Workload ID is designed specifically for non-human identities, it focuses on who gets a token and under what conditions:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Conditional Access for workload identities &lt;/STRONG&gt;— Restricts token issuance to specific public IP ranges and blocks requests when risk thresholds are crossed.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Identity Protection for workloads &lt;/STRONG&gt;— Detects risky service principals, including leaked credentials, and lets you investigate, confirm compromise, or disable the identity.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;App Health Recommendations &lt;/STRONG&gt;— Flags stale, inactive service principals and expiring secrets before attackers exploit them.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Access reviews &lt;/STRONG&gt;— Forces scheduled recertification for service principals holding privileged directory roles.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H5&gt;Layer 2 | Detect what Non-Human Identities do with Defender for Resource Manager&lt;/H5&gt;
&lt;P&gt;Even with strict front-door checks, a legitimate secret can still be abused. Microsoft Defender for Resource Manager provides a behavioral detection layer for the Azure management plane, analyzing Azure Resource Manager (ARM) operations for suspicious activity that may indicate an identity has been compromised.&lt;/P&gt;
&lt;P&gt;For Non-Human Identities, Microsoft provides dedicated &lt;STRONG&gt;service-principal behavioral detections&lt;/STRONG&gt; that look for suspicious use of high-risk Azure management operations. These detections span the attack lifecycle, including &lt;STRONG&gt;initial access, credential access, execution, persistence, privilege escalation, defense evasion, lateral movement, collection, and impact&lt;/STRONG&gt;. This allows Defender to identify scenarios where a service principal may have valid credentials and legitimate Azure RBAC permissions, but begins using those permissions in ways consistent with an attacker.&lt;/P&gt;
&lt;P&gt;When suspicious behavior is detected, it is surfaced as a &lt;STRONG&gt;Defender for Cloud security alert&lt;/STRONG&gt;, providing security teams with information about the detected activity, severity, and associated attack technique. Defender for Resource Manager can also detect surrounding indicators such as activity from suspicious IP addresses or TOR infrastructure, unusual privilege or role changes, abnormal resource creation, persistence activity, and known Azure exploitation techniques. Together, these signals help the SOC move beyond &lt;STRONG&gt;“Was this Non-Human Identity allowed to authenticate?”&lt;/STRONG&gt; to the more important question: &lt;STRONG&gt;“After authentication, is this identity behaving like the expected workload or like an attacker?”&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;A full list of the alerts provided by Microsoft Defender for Resource Manager is on the Defender for Cloud &lt;A href="https://learn.microsoft.com/en-us/azure/defender-for-cloud/alerts-resource-manager" target="_blank" rel="noopener"&gt;alerts reference page&lt;/A&gt;. [2]&lt;/P&gt;
&lt;H5&gt;Layer 3 | Give AI agents an identity, governance, and security plane with Microsoft Agent 365&lt;/H5&gt;
&lt;P&gt;Unlike a traditional application that executes a relatively predictable workflow, an agent can reason, invoke tools, access corporate data, interact with other services, and take actions on behalf of a user or itself. Organizations therefore need controls that extend beyond simply authenticating the underlying application.&amp;nbsp; Microsoft Agent 365 provides a control plane for discovering, governing, and securing agents across the organization:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Agent registry and inventory&lt;/STRONG&gt;: Establishes centralized visibility into registered agents so security and IT teams can identify agents operating across the environment rather than relying on individual development teams to track them. Connected platforms and the Agent 365 SDK extend visibility and management to agents built outside Microsoft's native agent platforms.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Purpose-built agent identity with Microsoft Entra Agent ID&lt;/STRONG&gt;: Gives agents a distinct identity foundation instead of treating every agent as an indistinguishable application or service principal. This allows security teams to apply controls to the agent itself and better understand which agent is requesting access.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Agent ownership and sponsorship&lt;/STRONG&gt;: Associates agents with accountable human sponsors. This creates an ownership model for non-human identities so an agent can be reviewed, governed, and ultimately disabled or removed when its sponsor, business purpose, or lifecycle changes.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Lifecycle governance&lt;/STRONG&gt;: Applies identity governance controls to agents so access does not have to become permanent simply because an agent was deployed. Organizations can govern the lifecycle from onboarding and access assignment through review and eventual removal.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Governed resource access&lt;/STRONG&gt;: Microsoft Entra governance capabilities such as access packages can be used to define which resources an agent should receive access to, who can request or approve that access, and how long the entitlement should remain.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Conditional Access for agents&lt;/STRONG&gt;: Agent-specific Conditional Access gives organizations another policy enforcement point for controlling how agent identities access protected resources. This helps move agent security away from implicit trust toward policy-based access.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Agent-aware protection across Microsoft security&lt;/STRONG&gt;: Agent 365 integrates the agent into Microsoft's broader security and compliance ecosystem, including Microsoft Defender and Microsoft Purview, so organizations can investigate agent-related threats, apply data security controls, and incorporate agents into existing security operations rather than creating a separate security program for AI.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Activity and observability&lt;/STRONG&gt;: Centralized agent visibility helps security and operations teams understand which agents exist, who sponsors them, what resources they can reach, and how they are interacting with the enterprise environment. This is critical when autonomous actions occur without a person directly initiating every transaction.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Beyond outlining Microsoft's multi-layer defense controls that organizations can implement to protect their NHIs from modern threats, below are practical principles and actionable steps, alongside Microsoft's official mitigation and protection guidance for Storm-3168.&lt;/P&gt;
&lt;H5&gt;&lt;STRONG&gt;&lt;U&gt;Core Principles to Harden Non-Human Identities&lt;/U&gt;&lt;/STRONG&gt;&lt;STRONG&gt;:&lt;/STRONG&gt;&lt;/H5&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;STRONG&gt;Prefer secretless authentication&lt;/STRONG&gt; — Use managed identities for Azure workloads, and Workload Identity Federation (OIDC) to swap short-lived tokens instead of storing static credentials.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Apply least privilege&lt;/STRONG&gt; — Give service principals only the specific roles and scopes they need. Avoid broad Owner or Contributor assignments.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Own and review them&lt;/STRONG&gt; — Assign clear owners. Regularly review privileged service principals and clean up unused apps and credentials.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Watch for risk signals&lt;/STRONG&gt; — Use Entra Workload ID Identity Protection features to detect leaked credentials and risky sign-in behavior, and pair that with monitoring of Azure resource operations.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Treat them like privileged accounts&lt;/STRONG&gt; — Even though they’re not people, high-privilege workload identities deserve the same rigor you apply to admin accounts: inventory, review, and rapid response.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;H5&gt;&lt;STRONG&gt;&lt;U&gt;Practical Steps to Harden Entra Workload Identities&lt;/U&gt;&lt;/STRONG&gt;&lt;STRONG&gt;:&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Secure access with adaptive policies&lt;/U&gt;:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Apply Conditional Access policies to service principals using&amp;nbsp;&lt;A href="https://learn.microsoft.com/en-us/entra/identity/conditional-access/workload-identity?toc=/azure/active-directory/workload-identities/toc.json&amp;amp;bc=/azure/active-directory/workload-identities/breadcrumb/toc.json" target="_blank" rel="noopener"&gt;Conditional Access for workload identities&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Enable real-time enforcement of Conditional Access location and risk policies using &lt;A href="https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-continuous-access-evaluation-workload?toc=/azure/active-directory/workload-identities/toc.json&amp;amp;bc=/azure/active-directory/workload-identities/breadcrumb/toc.json" target="_blank" rel="noopener"&gt;Continuous access evaluation for workload identities&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Manage &lt;A href="https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/custom-security-attributes-apps?toc=/azure/active-directory/workload-identities/toc.json&amp;amp;bc=/azure/active-directory/workload-identities/breadcrumb/toc.json" target="_blank" rel="noopener"&gt;custom security attributes for an app&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Intelligently detect compromised identities&lt;/U&gt;:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Detect risks (like leaked credentials), contain threats, and reduce risk to workload identities and agents using &lt;A href="https://learn.microsoft.com/en-us/entra/id-protection/concept-workload-identity-risk?toc=/azure/active-directory/workload-identities/toc.json&amp;amp;bc=/azure/active-directory/workload-identities/breadcrumb/toc.json" target="_blank" rel="noopener"&gt;Microsoft Entra ID Protection&lt;/A&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Simplify lifecycle management&lt;/U&gt;:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Access Microsoft Entra protected resources without needing to manage secrets for workloads that run on Azure using &lt;A href="https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/overview?toc=/azure/active-directory/workload-identities?toc=/azure/active-directory/workload-identities/toc.json&amp;amp;bc=/azure/active-directory/workload-identities/breadcrumb/toc.json" target="_blank" rel="noopener"&gt;managed identities&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Access Microsoft Entra protected resources without needing to manage secrets using &lt;A href="https://learn.microsoft.com/en-us/entra/workload-id/workload-identity-federation" target="_blank" rel="noopener"&gt;workload identity federation&lt;/A&gt; for supported scenarios such as GitHub Actions, workloads running on Kubernetes, or workloads running in compute platforms outside of Azure.&lt;/LI&gt;
&lt;LI&gt;Review service principals and applications that are assigned to privileged directory roles in Microsoft Entra ID using &lt;A href="https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-create-roles-and-resource-roles-review?toc=/azure/active-directory/workload-identities/toc.json&amp;amp;bc=/azure/active-directory/workload-identities/breadcrumb/toc.json" target="_blank" rel="noopener"&gt;access reviews for service principals&lt;/A&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;H5&gt;&lt;STRONG&gt;&lt;U&gt;Mitigation and Protection Guidance for Storm-3168: “Agentic-driven cloud attacks using compromised service principals”&lt;/U&gt;&lt;/STRONG&gt;&lt;/H5&gt;
&lt;UL&gt;
&lt;LI&gt;Enable appropriate Microsoft Defender for Cloud plans for critical Azure workloads. Consider enabling workload protections relevant to the resources in your environment, including Defender for Resource Manager, Defender for Storage, Defender for Key Vault, Defender for App Service and Defender for Databases. Learn more in the &lt;A href="https://learn.microsoft.com/en-us/azure/defender-for-cloud/defender-for-cloud-introduction" target="_blank" rel="noopener"&gt;Microsoft Defender for Cloud overview&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Protect and continuously assess application credentials and secrets. Avoid storing service principal credentials, storage keys, connection strings, and other secrets in source code, configuration files, public repositories, issues, or other locations where they might be inadvertently exposed. Learn more in the &lt;A href="https://learn.microsoft.com/en-us/entra/workload-id/" target="_blank" rel="noopener"&gt;Microsoft Entra Workload ID documentation&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Rotate compromised or exposed credentials immediately and establish credential lifecycle practices. Treat credentials that have been publicly exposed as compromised, even if the original location has subsequently been edited or deleted. Removing the content does not invalidate the credential or eliminate copies retained in edit history, caches, archives, logs, or other systems. Immediately revoke or rotate the affected credentials and investigate their historical use. Where supported, organizations should favor mechanisms that reduce reliance on long-lived credentials. Learn more about &lt;A href="https://learn.microsoft.com/en-us/azure/defender-for-cloud/secrets-scanning" target="_blank" rel="noopener"&gt;protecting secrets with Defender for Cloud&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Apply least privilege to service principals and other workload identities. Review the Azure RBAC permissions assigned to service principals and restrict their privileges to the resources and operations required by their applications. Learn more about &lt;A href="https://learn.microsoft.com/en-us/azure/role-based-access-control/best-practices" target="_blank" rel="noopener"&gt;best practices for Azure RBAC&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Protect backup and recovery infrastructure as part of ransomware resilience. Restrict access to backup and recovery resources and closely monitor attempts to modify or remove their protection controls. Learn more about &lt;A href="https://learn.microsoft.com/en-us/azure/backup/azure-backup-data-protection-best-practices" target="_blank" rel="noopener"&gt;Azure Backup security best practices&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Scale investigation and response with agentic defenses. Use &lt;A href="https://www.microsoft.com/security/business/ai-powered-cybersecurity/project-perception-agentic-system" target="_blank" rel="noopener"&gt;Project Perception&lt;/A&gt; to help defenders deploy AI agents that investigate and respond across large, complex environments at machine speed.&lt;/LI&gt;
&lt;LI&gt;Strengthen security posture for AI applications and agentic systems. Use Microsoft Defender for AI Security (&lt;A href="https://learn.microsoft.com/security-exposure-management/ai-code-security-overview" target="_blank" rel="noopener"&gt;codename MDASH&lt;/A&gt;) to discover AI assets, identify vulnerabilities and misconfigurations, and reduce exposure to AI-related attack paths.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;H5&gt;&lt;STRONG&gt;The Bottom Line&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;Non-Human Identities are no longer just “service accounts.” They are first-class identities that attackers actively target. Because they can’t use MFA and often lack strong lifecycle management, a single leaked secret or compromised pipeline can give an attacker lasting, high-impact access.&lt;/P&gt;
&lt;P&gt;Microsoft provides the multi-layer security controls to inventory, review, risk-assess, and restrict these non-human identities. Combined with least-privilege access, secretless authentication, and monitoring of what NHIs actually do in Azure, organizations can significantly reduce their risk to these identity-based attacks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;For additional details or assistance, please reach out to your Microsoft Representative.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Learn More:&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;For the latest security research from the Microsoft Threat Intelligence community, check out the &lt;A href="https://aka.ms/threatintelblog" target="_blank" rel="noopener"&gt;Microsoft Threat Intelligence Blog&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Review our documentation to learn how to prevent identity attacks, ensure least privilege access, unify access controls, and see how to enable them within your organization.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Learn more about &lt;A href="https://learn.microsoft.com/en-us/defender-cloud-apps/ai-agent-protection" target="_blank" rel="noopener"&gt;securing Copilot Studio agents with Microsoft Defender&lt;/A&gt; &lt;/LI&gt;
&lt;LI&gt;Evaluate your AI readiness with our latest &lt;A href="https://microsoft.github.io/zerotrustassessment/" target="_blank" rel="noopener"&gt;Zero Trust for AI workshop&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://learn.microsoft.com/en-us/copilot/microsoft-365/microsoft-365-copilot-ai-security" target="_blank" rel="noopener"&gt;Microsoft 365 Copilot AI security documentation&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://www.microsoft.com/en-us/security/blog/2024/04/11/how-microsoft-discovers-and-mitigates-evolving-attacks-against-ai-guardrails/" target="_blank" rel="noopener"&gt;How Microsoft discovers and mitigates evolving attacks against AI guardrails&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://learn.microsoft.com/en-us/defender-office-365/step-by-step-guides/prompt-injection-protection-defender-for-office-365" target="_blank" rel="noopener"&gt;Prompt injection protection in Microsoft Defender for Office 365 &lt;/A&gt;– official documentation of the prompt injection protection in Microsoft Defender for Office 365.&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://www.microsoft.com/en-us/security/blog/2024/04/11/how-microsoft-discovers-and-mitigates-evolving-attacks-against-ai-guardrails/" target="_blank" rel="noopener"&gt;How Microsoft discovers and mitigates evolving attacks against AI guardrails | Microsoft Security Blog&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://www.microsoft.com/en-us/security/blog/2026/02/10/ai-recommendation-poisoning/" target="_blank" rel="noopener"&gt;Manipulating AI memory for profit: The rise of AI Recommendation Poisoning | Microsoft Security Blog&lt;/A&gt; – a related example of an AI-era technique observed in email traffic&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/defending-the-inbox-against-prompt-injection-attacks/4534636" target="_blank" rel="noopener"&gt;Defending the inbox against prompt injection attacks | Microsoft Defender for Office 365 Blog &lt;/A&gt;– feature announcement introducing prompt injection protection in Microsoft Defender for Office 365.&lt;/LI&gt;
&lt;LI&gt;Learn how Microsoft is reimagining the SOC for the agentic era with &lt;A href="https://www.microsoft.com/security/blog/2026/09/23/reimagining-the-soc-for-the-agentic-era-in-microsoft-defender/" target="_blank" rel="noopener"&gt;ISOC in Microsoft Defender&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;⁠&lt;A href="https://www.microsoft.com/en-us/security/blog/products/microsoft-entra/" target="_blank" rel="noopener"&gt;Microsoft Entra News and Insights | Microsoft Security Blog&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://learn.microsoft.com/en-us/entra/" target="_blank" rel="noopener"&gt;Microsoft Entra documentation | Microsoft Learn&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;References:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;[1] Microsoft Corporation. &lt;A href="https://www.microsoft.com/en-us/security/blog/2026/09/25/storm-3168-agentic-driven-cloud-attacks-using-compromised-service-principals/" target="_blank" rel="noopener"&gt;Storm-3168: Agentic-driven cloud attacks using compromised service principals | Microsoft Security Blog&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2 Microsoft Corporation. &lt;A href="https://learn.microsoft.com/en-us/azure/defender-for-cloud/alerts-resource-manager" target="_blank" rel="noopener"&gt;Alerts for Resource Manager - Microsoft Defender for Cloud | Microsoft Learn&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Nov 2026 04:59:58 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/securing-the-non-human-identity-attack-surface/ba-p/4571497</guid>
      <dc:creator>Randall_Irwin</dc:creator>
      <dc:date>2026-11-09T04:59:58Z</dc:date>
    </item>
    <item>
      <title>Article 5 - The 90-Day Agent Governance Plan</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/article-5-the-90-day-agent-governance-plan/ba-p/4569604</link>
      <description>&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;By now, most organizations have had the conversation. &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;AI agents are coming, s&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;ome are already here, e&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;mployees are experimenting with them, business teams are building them, IT is trying to understand the landscape, security is asking what they can access, and data teams are discovering that years of information governance decisions suddenly matter so much more.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;And leadership is asking a reasonable question:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt; "&lt;/SPAN&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="Quote"&gt;So&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="Quote"&gt; what should we actually do?"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2,&amp;quot;335559738&amp;quot;:160}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The answer doesn't need to begin with a three-year transformation program.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;Start with 90 days—not to solve agent governance, but to establish the foundation for a repeatable operating model.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;Because the objective isn't to make every agent in the enterprise perfect. It's to move from:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;"We think people are using agents."&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;to:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;"We know what we have, who owns it, what it can reach, and how we're going to govern it."&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That's a very different starting position.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H2&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;90-day roadmap&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;at a glance&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H2&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The plan follows a simple sequence: Days 1–30 establish the baseline by inventorying agents, assigning ownership, and mapping connections. Days 31–60 strengthen the data foundation by reviewing access, sensitivity, ownership, and content lifecycle. Days 61–90 apply the model to one representative agent from identity and access through monitoring and retirement.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="1"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt;Days 1–30: &lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt;Establish&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt; the baseline&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:360,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The first month is about &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;discovery&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;. Resist the temptation to start by writing a 40-page agent policy. Start by finding out what's actually happening.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;Inventory the agents&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H4&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;What agents already exist? Don't limit the exercise to formally approved projects. Look across the environment for the agents people are creating and using.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;You want to establish a baseline.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;Capture each agent’s purpose, creator, accountable owner, connected systems, data sources, and current operating status.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;You may discover that your organization has more agents than anyone realized. That's not necessarily bad news, that's useful information. You can't govern an unknown population.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;Identify&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt; the owners&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H4&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Once you know what exists, determine who is accountable. Some agents will have obvious business owners, others will have a technical creator but no clear business sponsor. Some may turn out to be experiments that nobody is using anymore. That's exactly the kind of information the baseline should uncover. The question isn't simply:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="Quote"&gt;"Who built this?"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2,&amp;quot;335559738&amp;quot;:160}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;It's:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="Quote"&gt;"Who is accountable for this continuing to exist?"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2,&amp;quot;335559738&amp;quot;:160}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That distinction becomes increasingly important as agents move from experimentation into business operations.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;Map the connections&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H4&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;An inventory tells you what exists. The next step is understanding relationships.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;What does each agent connect to?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Which applications?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Which sites?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Which information sources?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Which identities?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Which services?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This progression leads toward an agent map: a view of the relationships among agents, users, applications, and data. &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;This is where the first 30 days begin to produce something more valuable than a list. &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;They produce &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;context&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt;Days 31–60: Fix the data underneath the agents&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:360,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Once you understand the agent population, don't immediately try to lock everything down.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;Look underneath it.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The second month focuses on strengthening the data foundation. Review access on priority sites, apply sensitivity labels, retire content with no accountable owner, and establish clear ownership for the information agents depend on.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;In other words: &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;Fix the data foundation where it matters most.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;Start with the most important sites&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H4&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Don't try to clean the entire enterprise. Identify the repositories supporting your highest-value agent use cases.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;Then ask:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Who owns this information?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Who can access it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Is that access still appropriate?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Is the information sensitive?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Is the information still current?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Does this content still need to exist?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This is not a prerequisite for every AI experiment; it's targeted preparation for the places where agent adoption is becoming real.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;Retire what nobody owns&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H4&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;One of the most valuable outcomes of this exercise may be identifying obsolete or unowned information that remains accessible.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Old project sites.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Abandoned content.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Outdated documents.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Repositories with no clear owner.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Information that exists because nobody ever decided to remove it.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;The recommendation is simple: retire content nobody owns. That is sound information governance whether or not an agent ever touches the data.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Agents make it more urgent because they can surface unowned, outdated, or unnecessary information through conversational interfaces, expanding the risk of inaccurate or inappropriate use.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;If an organization is going to make more of its information discoverable through conversational interfaces, the question of whether that information should still exist becomes harder to ignore.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt;Days 61–90: Govern one agent end-to-end&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:360,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This is the most important part of the plan.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;Choose one meaningful agent—not the most complicated one or the one with the largest architecture diagram, but one that represents the type of agent the organization expects to deploy broadly.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;Then govern it from beginning to end.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4&gt;&lt;SPAN style="color: rgb(30, 30, 30);"&gt;Give it an identity&lt;/SPAN&gt;&lt;/H4&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;You should know exactly which agent you're dealing with.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;It shouldn't be an anonymous piece of automation hidden somewhere in the environment. &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;&lt;STRONG&gt;Identify it&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4&gt;&lt;SPAN style="color: rgb(30, 30, 30);"&gt;Give it an owner&lt;/SPAN&gt;&lt;/H4&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Assign a named sponsor and owner.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;Someone should be accountable for its business purpose and continued operation.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;&lt;STRONG&gt;Own it&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4&gt;&lt;SPAN style="color: rgb(30, 30, 30);"&gt;Scope its access&lt;/SPAN&gt;&lt;/H4&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Document what the agent needs to reach. Then remove what it doesn't need.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;The principle is familiar:&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;Least privilege.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;The agent should have enough access to accomplish its defined purpose—and no more. Granting access for conceivable future uses expands risk without supporting the current business need.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;&lt;STRONG&gt;Scope it&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4&gt;&lt;SPAN style="color: rgb(30, 30, 30);"&gt;Understand its data&lt;/SPAN&gt;&lt;/H4&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Know which information sources it depends on.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;Make sure those sources have appropriate access and protection. If the agent is operating against sensitive information, understand the implications.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;&lt;STRONG&gt;Protect the data around it&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4&gt;&lt;SPAN style="color: rgb(30, 30, 30);"&gt;Watch what it does&lt;/SPAN&gt;&lt;/H4&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Establish visibility into activity and usage.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Can you tell whether the agent is actually being used?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Can you understand its connections?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Can you identify unusual or concerning activity?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Can security investigate when necessary?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The objective isn't surveillance for its own sake. It's operational visibility.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;&lt;STRONG&gt;Watch it&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4&gt;&lt;SPAN style="color: rgb(30, 30, 30);"&gt;Define its exit&lt;/SPAN&gt;&lt;/H4&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Finally, answer a question organizations frequently forget until it's too late:&lt;/SPAN&gt; &lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="Quote"&gt;When does this agent stop existing?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2,&amp;quot;335559738&amp;quot;:160}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;What happens when the business process changes?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;When the owner leaves?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;When the agent is replaced?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;When nobody uses it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;When its data sources change?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Define the retirement path before you need it.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;&lt;STRONG&gt;Retire it&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt;What you should have after&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt;90 days&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:360,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The goal is not a perfect agent governance program. It is a repeatable operating model that shows what agents exist, who owns them, what data they use, and how one representative agent is governed across its lifecycle.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;&lt;STRONG&gt;A repeatable model&lt;/STRONG&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;After 90 days, you should be able to demonstrate:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-level="3"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 3"&gt;A baseline&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt; - &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;You have a picture of the agent population.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI aria-level="3"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 3"&gt;Accountability&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt; - &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;You know who owns the agents that matter.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI aria-level="3"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 3"&gt;Data readiness&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt; - &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;You've addressed the most important underlying data governance issues.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI aria-level="3"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 3"&gt;A governed example&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt; - &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;You've taken at least one meaningful agent through the complete lifecycle.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI aria-level="3"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 3"&gt;A repeatable framework&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt; - &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;You now know how to apply the same controls to the next agent.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That's the beginning of an operating model.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;The operating model begins with a practical sequence: discover the agent landscape, strengthen the information foundation, govern one representative agent, and scale the pattern.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="1"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt;Don't&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt; make the 90-day plan a technology project&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:360,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;There's an important distinction here. This isn't fundamentally about buying another tool. Tools can help with discovery, identity, access control, data protection, monitoring and lifecycle management.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;But the first question is organizational:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="Quote"&gt;What does "&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="Quote"&gt;governed&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="Quote"&gt;" mean for an agent in our environment?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2,&amp;quot;335559738&amp;quot;:160}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;If the answer isn't clear, technology won't solve the ambiguity. That's why the sequence matters.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Discover.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Understand.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Fix the foundation.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Govern one.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Scale the pattern.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt;Ask for the sequence, not the decision&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:360,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;There's a useful leadership lesson buried in all of this.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;When an organization is facing a new technology, executives often ask for a decision:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="Quote"&gt;"Are we ready for agents?"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2,&amp;quot;335559738&amp;quot;:160}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That's almost impossible to answer as a binary question.&lt;/SPAN&gt; &lt;SPAN data-contrast="auto"&gt;A better question is:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="Quote"&gt;"What's the sequence that gets us ready?"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2,&amp;quot;335559738&amp;quot;:160}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Ask for the sequence, not a binary decision. For emerging technology, readiness develops through action: understand the agent landscape, learn how the organization uses it, fix the foundation, govern one representative agent, and scale what works.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;You need to know what you're going to learn first.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Then what you'll fix.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Then what you'll govern.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Then how you'll scale.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt;The&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt;90 days&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt; are the beginning, not the destination&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:360,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;After the first 90 days, the work continues.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;The agent population will grow.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;New capabilities will emerge.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;New data sources will be connected.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;New risks will appear.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Some agents will become critical business infrastructure.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Others will disappear.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Lifecycle governance is a continuing discipline, not a final state called “Agent Governance Complete.” The objective is to establish a lifecycle that keeps working as agents, data sources, capabilities, and risks change.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt;Inventory it. &lt;/SPAN&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt;Identify&lt;/SPAN&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt; it. Own it. Scope it. Watch it. Retire it.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Then do it again.&lt;/SPAN&gt; &lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt;We've&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="heading 1"&gt; done this before, and t&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;hat's ultimately the message of this series. We didn't learn how to govern enterprise assets overnight, we learned through successive waves.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Identity&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Devices&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Applications&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Data&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;And now agents&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Each wave introduced new technology and new risks but the organization eventually developed a way to bring that technology into an operating model.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Agents are the fifth major governance wave. Organizations do not have to start from zero; they can adapt lessons from identity, device, application, and data governance. The starting point is not a massive transformation program, a perfect policy, or a prediction about where AI will be five years from now.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3&gt;&lt;SPAN data-contrast="auto"&gt;With 90 days&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Thirty days to understand what you have.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Thirty days to improve the data underneath it.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN data-contrast="auto"&gt;Thirty days to govern one agent from beginning to end.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Then take what you learned and scale it because the goal isn't to govern the future, it's to start governing what you already have.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;SPAN data-contrast="auto"&gt;This is the fifth and final article in the initial series exploring the "fifth lifecycle" of enterprise IT: the governance of AI agents alongside identity, devices, applications and data.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Nov 2026 15:36:10 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/article-5-the-90-day-agent-governance-plan/ba-p/4569604</guid>
      <dc:creator>Chad Stout</dc:creator>
      <dc:date>2026-11-02T15:36:10Z</dc:date>
    </item>
    <item>
      <title>Before You Manage AI Agents, Look at How You Manage Applications</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/before-you-manage-ai-agents-look-at-how-you-manage-applications/ba-p/4565936</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Watch the video:&lt;/STRONG&gt; &lt;EM&gt;From Application Sprawl to Agent Sprawl: Microsoft Agent 365 Explained&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Select the video below to explore the idea in under three minutes.&lt;/EM&gt;&lt;/P&gt;
&lt;div data-video-id="https://www.youtube.com/watch?v=11yaIiBTQps/1792434369578" data-video-remote-vid="https://www.youtube.com/watch?v=11yaIiBTQps/1792434369578" class="lia-video-container lia-media-is-center lia-media-size-large"&gt;&lt;iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F11yaIiBTQps%3Ffeature%3Doembed&amp;amp;display_name=YouTube&amp;amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D11yaIiBTQps&amp;amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F11yaIiBTQps%2Fhqdefault.jpg&amp;amp;type=text%2Fhtml&amp;amp;schema=youtube" allowfullscreen="" style="max-width: 100%"&gt;&lt;/iframe&gt;&lt;/div&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;Start with the application estate&lt;/H4&gt;
&lt;P&gt;Before asking how an organization should manage hundreds or thousands of agents, it helps to examine how it manages applications today.&lt;/P&gt;
&lt;P&gt;For every important application, IT should be able to answer questions such as:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Who owns it?&lt;/LI&gt;
&lt;LI&gt;Who uses it?&lt;/LI&gt;
&lt;LI&gt;What business process does it support?&lt;/LI&gt;
&lt;LI&gt;What data does it access?&lt;/LI&gt;
&lt;LI&gt;Which identities and permissions does it require?&lt;/LI&gt;
&lt;LI&gt;Which devices is it allowed to run on?&lt;/LI&gt;
&lt;LI&gt;Which networks and external services can it reach?&lt;/LI&gt;
&lt;LI&gt;Where is it deployed?&lt;/LI&gt;
&lt;LI&gt;How is its activity monitored?&lt;/LI&gt;
&lt;LI&gt;Is it still needed?&lt;/LI&gt;
&lt;LI&gt;When and how will it be retired?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;These questions span application lifecycle management, identity, endpoint management, networking, data governance, security, compliance, and operations.&lt;/P&gt;
&lt;P&gt;They also require relationships to be understood. An application is not simply an entry in a software inventory. It is connected to people, devices, departments, locations, business processes, infrastructure, and data.&lt;/P&gt;
&lt;P&gt;This is why the CMDB becomes more valuable when it is treated as a living map rather than a static list of assets.&lt;/P&gt;
&lt;H4&gt;Apply the same thinking to agents&lt;/H4&gt;
&lt;P&gt;An AI agent may look different from a traditional application, but many of the management questions remain the same.&lt;/P&gt;
&lt;P&gt;For each agent, an organization should understand:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Who created and owns it?&lt;/LI&gt;
&lt;LI&gt;Who is allowed to use it?&lt;/LI&gt;
&lt;LI&gt;What task is it designed to perform?&lt;/LI&gt;
&lt;LI&gt;What identity does it use?&lt;/LI&gt;
&lt;LI&gt;Is it acting independently or on behalf of a person?&lt;/LI&gt;
&lt;LI&gt;What applications, APIs, and tools can it call?&lt;/LI&gt;
&lt;LI&gt;What data can it read, create, modify, or share?&lt;/LI&gt;
&lt;LI&gt;Which devices, networks, and environments can it operate in?&lt;/LI&gt;
&lt;LI&gt;How is its activity observed and audited?&lt;/LI&gt;
&lt;LI&gt;What happens when its owner changes roles or leaves?&lt;/LI&gt;
&lt;LI&gt;When should the agent be reviewed, updated, blocked, or retired?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Agents introduce additional complexity because they can take actions—not merely display information. They may chain tools together, operate across systems, interact with other agents, and make decisions based on changing context.&lt;/P&gt;
&lt;P&gt;That makes ownership, permissions, monitoring, and lifecycle management even more important.&lt;/P&gt;
&lt;H4&gt;Application lifecycle management is the starting point&lt;/H4&gt;
&lt;P&gt;Organizations do not need to invent every aspect of agent lifecycle management from scratch.&lt;/P&gt;
&lt;P&gt;The disciplines already used for applications provide a useful foundation:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Discover&lt;/STRONG&gt; what exists.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Categorize&lt;/STRONG&gt; it by purpose, owner, risk, and data access.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Plan&lt;/STRONG&gt; the appropriate controls.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Deploy&lt;/STRONG&gt; it to approved users and environments.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Measure&lt;/STRONG&gt; usage, value, health, and risk.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Review&lt;/STRONG&gt; it as technology and business requirements change.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Retire&lt;/STRONG&gt; it when it is no longer needed.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The technology may be new, but the need to understand what exists has not changed.&lt;/P&gt;
&lt;H4&gt;Moving from visibility to control&lt;/H4&gt;
&lt;P&gt;The first step is creating visibility across the agent estate.&lt;/P&gt;
&lt;P&gt;Organizations need a way to see which agents are available, where they came from, who owns them, how they are being used, what they can access, and how they relate to the rest of the environment.&lt;/P&gt;
&lt;P&gt;That is the role Microsoft Agent 365 is designed to support: providing a control plane for observing, governing, and securing agents with the Microsoft identity, security, compliance, and management capabilities organizations already use.&lt;/P&gt;
&lt;P&gt;The objective is not to slow down AI innovation. It is to make responsible innovation possible at enterprise scale.&lt;/P&gt;
&lt;H4&gt;Map today to manage tomorrow&lt;/H4&gt;
&lt;P&gt;The central idea is simple:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;You cannot manage tomorrow if you cannot map today.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Organizations that understand their current applications, endpoints, identities, networks, business processes, and data dependencies will be better positioned to manage agents as they become part of everyday work.&lt;/P&gt;
&lt;P&gt;Before asking how many agents the organization can build, start with a more important question:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;How well do we understand—and manage—the technology estate we already have?&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Oct 2026 14:06:47 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/before-you-manage-ai-agents-look-at-how-you-manage-applications/ba-p/4565936</guid>
      <dc:creator>NicholasAquino</dc:creator>
      <dc:date>2026-10-21T14:06:47Z</dc:date>
    </item>
    <item>
      <title>Article 4 - Governance Is the Permission Slip</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/article-4-governance-is-the-permission-slip/ba-p/4565905</link>
      <description>&lt;P&gt;A familiar pattern emerges whenever a new technology enters the enterprise: the business sees opportunity, IT sees complexity, security sees risk, and governance sees a problem. Soon, someone says, “We need a policy before anyone can use this.”&lt;/P&gt;
&lt;P&gt;That instinct is understandable, but it can become a trap. When governance becomes synonymous with waiting, the business rarely stops innovating; it finds another path. We saw this with cloud services, mobile devices, applications, and data. AI agents will be no different. Governance should not be the brake on agent adoption, it should be the permission slip.&lt;/P&gt;
&lt;H2&gt;Why the Governance Model Must Change&lt;/H2&gt;
&lt;H3&gt;Adoption is already ahead of governance&lt;/H3&gt;
&lt;P&gt;Microsoft research on agent adoption and security found that 42% of organizations had deployed at least some agents, 78% were concerned about agent cybersecurity, and 76% of leaders expected employees to manage agents within two to three years. The exact figures will change as adoption matures, but the pattern is clear: organizations are moving toward agents while many are still deciding how those agents should be governed.&lt;/P&gt;
&lt;P&gt;That creates a choice. Organizations can try to slow adoption until governance catches up, or they can build governance that makes responsible adoption possible. The second approach is more durable because governance is too important to reduce to a gate at the end of the process.&lt;/P&gt;
&lt;H3&gt;The limits of governance as a gate&lt;/H3&gt;
&lt;P&gt;The traditional model is sequential:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Someone requests permission to use a new technology.&lt;/LI&gt;
&lt;LI&gt;Security, architecture, legal, compliance, and IT review the request.&lt;/LI&gt;
&lt;LI&gt;After several handoffs, someone makes a decision.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;This model can work when technology adoption is centralized and the number of deployments is manageable. Agents challenge that assumption. If thousands of employees can create, configure, or use agents, every agent cannot be treated as a bespoke technology project. The scale changes the economics of governance. Organizations need guardrails that operate across an entire agent population.&lt;/P&gt;
&lt;H2&gt;Governance as a Framework&lt;/H2&gt;
&lt;P&gt;Instead of asking, “How do we approve every agent?” ask, “What conditions must be true for an agent to operate safely?”&lt;/P&gt;
&lt;P&gt;Inventory it. Identify it. Own it. Scope it. Watch it. Retire it.&lt;/P&gt;
&lt;P&gt;These lifecycle steps become the conditions for participation. An agent may not need a committee meeting every time it is created, but the organization must be able to answer:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Inventory:&lt;/STRONG&gt; What is the agent, and where does it operate?&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Identity:&lt;/STRONG&gt; What identity does it use?&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Ownership:&lt;/STRONG&gt; Who sponsors and owns it?&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Scope:&lt;/STRONG&gt; What can it access and do?&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Data:&lt;/STRONG&gt; What information does it depend on?&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Observation:&lt;/STRONG&gt; How is its activity monitored and understood?&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Protection:&lt;/STRONG&gt; How are threats and sensitive data handled?&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Lifecycle:&lt;/STRONG&gt; When should the agent be reviewed, expire, or be retired?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;That is governance as infrastructure, not governance as paperwork.&lt;/P&gt;
&lt;H3&gt;The permission slip has conditions&lt;/H3&gt;
&lt;P&gt;A permission slip is not permission to do anything. It is permission to operate within defined boundaries. For AI agents, those boundaries should include:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Known identity:&lt;/STRONG&gt; Every agent has an identifiable identity.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Clear accountability:&lt;/STRONG&gt; Every agent has a named sponsor and owner.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Least-privilege access:&lt;/STRONG&gt; Access is limited to what the agent needs.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Protected data:&lt;/STRONG&gt; The agent uses information with appropriate access, classification, and protection.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Operational visibility:&lt;/STRONG&gt; Activity, connections, and changes can be understood.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Integrated security:&lt;/STRONG&gt; Threat detection and data protection are part of the operating environment.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Defined lifecycle:&lt;/STRONG&gt; The agent can be reviewed, expired, and retired.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;These are not barriers to adoption. They are the conditions that make adoption governable.&lt;/P&gt;
&lt;H2&gt;Designing Governance for Scale&lt;/H2&gt;
&lt;H3&gt;The goal is manageable risk—not zero risk&lt;/H3&gt;
&lt;P&gt;No technology adoption model eliminates risk. The executive question is whether the organization can understand and manage the risk it accepts. That requires moving from “Agents are risky, so we must control them” to “Agents have predictable governance requirements, so we will build those requirements into how they operate.”&lt;/P&gt;
&lt;P&gt;This creates a healthier relationship among stakeholders. The business gets a clear path to adoption. IT gains visibility. Security gains enforceable boundaries. Information governance becomes part of the operating model. Leadership gains measurable controls.&lt;/P&gt;
&lt;H3&gt;Good governance makes “yes” easier&lt;/H3&gt;
&lt;P&gt;The better the governance framework becomes, the easier it is to approve responsible use. Under a gate-based model, an employee who wants to create an agent hears, “Let’s review it.” Under a framework-based model, the answer can be:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Yes, provided the agent has an identity, an owner, scoped access, approved data sources, appropriate monitoring, and a defined lifecycle.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The organization is not saying, “Do not build it.” It is saying, “Here is how to build it responsibly.” That distinction matters.&lt;/P&gt;
&lt;H3&gt;Guardrails should be reusable&lt;/H3&gt;
&lt;P&gt;If every agent requires a new interpretation of security policy, the governance team becomes the bottleneck. Reusable controls turn governance from a series of one-off decisions into a scalable operating system.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Gate model:&lt;/STRONG&gt; One agent, one review, one decision.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Framework model:&lt;/STRONG&gt; One control framework, thousands of governed agents.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The second model resembles how mature IT organizations already govern identities, devices, applications, and data. The goal is not to inspect everything manually forever. It is to create enough structure for the environment to remain visible, accountable, and controlled at scale.&lt;/P&gt;
&lt;H2&gt;Connecting Governance to the Fifth Lifecycle&lt;/H2&gt;
&lt;P&gt;The first three articles in this series established a progression:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;A class="lia-internal-link lia-internal-url lia-internal-url-content-type-blog" href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/the-fifth-lifecycle-ai-agents-are-the-new-enterprise-asset-class/4559961" data-lia-auto-title="Article 1: Agents are the fifth enterprise asset class" data-lia-auto-title-active="0" target="_blank"&gt;&lt;STRONG&gt;Article 1:&lt;/STRONG&gt; Agents are the fifth enterprise asset class&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;&lt;A class="lia-internal-link lia-internal-url lia-internal-url-content-type-blog" href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/the-questions-never-change/4561652" data-lia-auto-title="Article 2: The governance questions have not changed" data-lia-auto-title-active="0" target="_blank"&gt;&lt;STRONG&gt;Article 2:&lt;/STRONG&gt; The governance questions have not changed&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;&lt;A class="lia-internal-link lia-internal-url lia-internal-url-content-type-blog" href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/article-3-your-agent-isn%E2%80%99t-the-data-problem/4563926" data-lia-auto-title="Article 3: Agent governance depends on the data underneath it" data-lia-auto-title-active="0" target="_blank"&gt;&lt;STRONG&gt;Article 3:&lt;/STRONG&gt; Agent governance depends on the data underneath it&lt;/A&gt;.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;The next connection is straightforward: governance is what allows the lifecycle to operate at scale.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Inventory without ownership is not governance.&lt;/LI&gt;
&lt;LI&gt;Ownership without scope is not governance.&lt;/LI&gt;
&lt;LI&gt;Scope without observation is not governance.&lt;/LI&gt;
&lt;LI&gt;Observation without retirement is not governance.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The controls must work together. That is the difference between having a policy and having a governance system.&lt;/P&gt;
&lt;H3&gt;Use durable principles, not predictions&lt;/H3&gt;
&lt;P&gt;IT cannot know exactly what the technology landscape will look like five years from now, but the governance model still needs to work. The most durable controls are therefore principle-based:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Every asset needs an identity.&lt;/LI&gt;
&lt;LI&gt;Every asset needs accountability.&lt;/LI&gt;
&lt;LI&gt;Every asset needs appropriate scope.&lt;/LI&gt;
&lt;LI&gt;Every asset needs observation.&lt;/LI&gt;
&lt;LI&gt;Every asset needs protection.&lt;/LI&gt;
&lt;LI&gt;Every asset needs an exit.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;These principles survive changes in implementation and give the organization room to innovate without restarting the governance conversation whenever the technology changes.&lt;/P&gt;
&lt;H2&gt;Make the Permission Slip Visible&lt;/H2&gt;
&lt;P&gt;Employees should not have to guess what they are allowed to build. Business leaders should not have to guess what IT will permit. Security should not discover agents only after deployment. A mature agent program makes the path explicit:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;What employees may build.&lt;/LI&gt;
&lt;LI&gt;What data they may use.&lt;/LI&gt;
&lt;LI&gt;What access they may request.&lt;/LI&gt;
&lt;LI&gt;Who must own the agent.&lt;/LI&gt;
&lt;LI&gt;How the agent will be monitored and protected.&lt;/LI&gt;
&lt;LI&gt;What happens when it reaches the end of its useful life.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;That is what a permission slip looks like in an enterprise: not a signature on paper, but a defined path to responsible action.&lt;/P&gt;
&lt;H3&gt;The real choice is governed or unmanaged adoption&lt;/H3&gt;
&lt;P&gt;The choice is not governance versus innovation. It is governed adoption versus unmanaged adoption. People will find ways to use AI. The strategic question is whether those uses become part of an environment the organization can understand, secure, and improve—or another layer of technology operating outside the control plane.&lt;/P&gt;
&lt;P&gt;Do not build a wall around agents. Build a control plane around them.&lt;/P&gt;
&lt;H2&gt;Governance Earns the Right to Say Yes&lt;/H2&gt;
&lt;P&gt;The phrase “permission slip” communicates two ideas at once: &lt;STRONG&gt;you may proceed&lt;/STRONG&gt;, and &lt;STRONG&gt;there are conditions&lt;/STRONG&gt;. That is the relationship enterprise governance should have with agent adoption. The posture should not be, “No, because we do not understand this yet.” It should be, “Yes—and here is the framework that lets us do it responsibly.” This shift is essential as agents move from experiments into everyday business operations.&lt;/P&gt;
&lt;P&gt;Identity, devices, applications, and data all needed governance. Agents need it too—not to stop the organization from moving, but to make movement possible without sacrificing visibility, accountability, or control. So do not ask, “How do we stop employees from creating agents?” Ask, “What must be true for us to let them do it confidently?” Then build those conditions. That is governance doing its real job: not the brake, but the permission slip.&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;This is the fourth article in a series exploring the “fifth lifecycle” of enterprise IT: governing AI agents alongside identity, devices, applications, and data.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Oct 2026 16:51:23 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/article-4-governance-is-the-permission-slip/ba-p/4565905</guid>
      <dc:creator>Chad Stout</dc:creator>
      <dc:date>2026-10-19T16:51:23Z</dc:date>
    </item>
    <item>
      <title>Article 3: Your Agent Isn’t the Data Problem</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/article-3-your-agent-isn-t-the-data-problem/ba-p/4563926</link>
      <description>&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;When organizations begin discussing AI agents, one question comes up immediately: What data will the agent be able to access?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That question matters. But a more uncomfortable one sits beneath it: What data can the employee already access?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;In many enterprise environments, the agent does not create the underlying access problem. It exposes it—and that distinction matters.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Agent readiness depends on data readiness. Organizations should govern the information their agents use with the same discipline they apply to the agents themselves.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;The agent &lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;didn’t&lt;/SPAN&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt; overshare your SharePoint site&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Imagine an employee asks an agent a reasonable question: “What decisions were made during last year’s project meetings?” The agent searches the knowledge sources available in that employee’s context, finds relevant documents, meeting information, and files, and produces an answer.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The immediate reaction may be: The AI accessed all that information.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;In this scenario, that is not necessarily what happened. The agent grounds the request in the knowledge sources available to the person asking and limits the response to content that person can access. Other agent designs and connected systems may use different identities or permission models, so organizations should verify how each agent authorizes access.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The agent did not necessarily create access; it reflected access that already existed. That is both the good news and the warning.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;AI removes the obscurity from weak permissions&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;For years, an organization could maintain an overshared repository without anyone noticing. A document may have overly broad permissions. A project site may still contain information from five years ago. A former employee may remain in a group. A library may hold sensitive material that was never classified. A site may have no clear business owner.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;None of these problems requires AI. They are information governance problems that often remain hidden because people are inefficient at discovering everything they can already access. We search for what we need, open the documents we know, and work within familiar systems.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;An agent changes that interaction model. Instead of navigating information manually, a person can ask a question in natural language. The obscurity disappears. Agents do not necessarily broaden permissions, but they can make existing permissions far more consequential.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Your agent inherits your data governance.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; If your content has no lifecycle, your agent inherits the absence of one.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;An agent cannot compensate for missing governance. If no one knows what information exists, owns it, reviews its access, classifies its sensitivity, or retires obsolete content, the agent must operate across an uncertain information estate. The problem may not be a poorly governed agent; it may be an environment that was never governed in the first place.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;Five consequences of data without a lifecycle&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;When information has no lifecycle, organizations face five predictable consequences:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="8" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Visibility:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; You do not know what information you have.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="8" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Ownership:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; No one is clearly accountable for it.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="8" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Control:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; Access is inherited rather than intentional.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="8" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Insight:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; You cannot easily see how information is used.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="8" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Disposition:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; Obsolete content is forgotten instead of retired.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;These are not AI problems. They are information governance problems—and AI raises the stakes.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;The data lifecycle comes before the agent lifecycle&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Enterprises already manage lifecycles for four critical asset classes:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="7" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Identity&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="7" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Devices&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="7" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Applications&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="7" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Data&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Agents now need a lifecycle as well. But these lifecycles are not independent; an agent depends on the assets beneath it:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="6" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Identity:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; Its identity depends on identity governance.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="6" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Access:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; Its access depends on access governance.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="6" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Connections:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; Its connections depend on application governance.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;What an agent can discover, summarize, generate, and send depends heavily on data governance. Organizations should treat agent governance as a fresh start only after assessing the health of the lifecycles beneath the agent and addressing the highest-risk gaps in identity, access, connections, and data.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The order matters: first understand and govern the information estate, then define how agents will use it. Agent-level controls are essential, but they cannot correct unowned content, stale permissions, or missing retention decisions.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;The harder inventory is the information beneath the agent&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;When organizations prepare for agents, they naturally want to discover and catalog the agents themselves. That is necessary—but it is not sufficient.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Inventory the information those agents will encounter.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Start with the repositories that matter most. Identify where sensitive information lives, where access is broad, where reviews are overdue, where content is stale, and where ownership or classification is unclear. Prioritize the conditions that create the greatest business, security, compliance, and privacy risk. The agent lifecycle requires a healthy data foundation.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;Start with the data that matters most&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;You do not need to solve every data governance problem before using an agent; for most large organizations, that would be an impossible prerequisite. The practical goal is to govern the information that matters most to the business processes where agents will operate.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Instead, focus on the business processes where agents will operate. Identify the repositories and data sources those processes depend on, then ask five questions:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Inventory:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; What information and content do we have?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Ownership:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; Who is accountable for it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Access:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; Who can access it, and is that access intentional?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Value:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; Is it current and still needed?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Disposition:&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; What should happen when it is no longer needed?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This is the same governance pattern established in the previous article, applied to the data beneath the agent.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;The paradox of AI governance&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The paradox is simple: the more useful agents become, the more important existing data governance becomes.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;A trivial agent needs little information. A genuinely useful enterprise agent usually needs much more:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="3" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Context&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="3" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Knowledge&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="3" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Access to systems&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="3" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Information from across the organization&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The business value of an agent is increasingly tied to the quality and accessibility of the organization’s information estate. But broader access also increases the consequences of stale, overshared, poorly classified, or ownerless content. The answer is not to make the agent blind; it is to make the information environment intentional.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;The real question is not “Can the agent see it?”&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Agent governance should not be reduced to a binary access question. Better questions include:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Lifecycle:&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt; Should this information still exist, and does the business still need it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Access:&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt; Should this person still have access?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Ownership:&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt; Is someone accountable for it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Classification:&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt; Is it appropriately classified?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Intent:&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt; Is the access intentional?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="6" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Currency:&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt; Is the information current?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Only after answering these questions does agent access become meaningful. An agent with properly scoped access to well-governed information is fundamentally different from one operating across years of unmanaged enterprise content.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;AI does not replace data governance&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;AI makes weak data governance harder to ignore. Organizations do not need perfect classification, ownership, and permissions before experimenting with agents, but they do need to recognize the dependency: agent governance cannot be stronger than the data governance beneath it. Agents do not create the underlying data problem; they make it visible so the organization can begin fixing it.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;The fifth lifecycle starts beneath the agent&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Identity. Devices. Applications. Data. Agents.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Five enterprise asset classes. Five interconnected lifecycles. Each new layer depends on the ones beneath it. To prepare agents for enterprise data, begin with the information that matters most and follow a deliberate sequence:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="5" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Find it.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="5" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Classify it.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="5" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Assign ownership.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="5" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Review access.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="5" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Retire what no longer belongs.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Agents inherit the information environment beneath them. The goal is not to help smarter agents navigate unmanaged content; it is to build governed agents on governed information.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;SPAN data-contrast="auto"&gt;This is the third article in a series exploring the “fifth lifecycle” of enterprise IT: governing AI agents alongside identities, devices, applications, and data.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Oct 2026 14:49:30 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/article-3-your-agent-isn-t-the-data-problem/ba-p/4563926</guid>
      <dc:creator>Chad Stout</dc:creator>
      <dc:date>2026-10-13T14:49:30Z</dc:date>
    </item>
    <item>
      <title>The New Microsoft Copilot:</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/the-new-microsoft-copilot/ba-p/4563898</link>
      <description>&lt;P&gt;The way we work with AI is evolving quickly.&lt;/P&gt;
&lt;P&gt;Microsoft recently introduced the new Microsoft Copilot experience, bringing together new ways to &lt;STRONG&gt;ask, delegate, build and automate work&lt;/STRONG&gt; while giving organizations additional controls for managing AI usage and spend.&lt;/P&gt;
&lt;P&gt;In our recent webinar, &lt;STRONG&gt;“New Microsoft Copilot App: Which Mode to Use, What It Costs, and Who Gets Access,”&lt;/STRONG&gt; we took a closer look at what these changes mean for organizations and the people using Copilot every day.&lt;/P&gt;
&lt;P&gt;Rather than trying to recreate the entire session here, this post highlights some of the major topics we covered. For the demonstrations, examples and deeper discussion, watch the accompanying webinar recording.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;div data-video-id="https://youtu.be/VHMf2iURkzo/1791828688171" data-video-remote-vid="https://youtu.be/VHMf2iURkzo/1791828688171" class="lia-video-container lia-media-is-center lia-media-size-large"&gt;&lt;iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DVHMf2iURkzo&amp;amp;type=text%2Fhtml&amp;amp;schema=youtube&amp;amp;display_name=YouTube&amp;amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FVHMf2iURkzo" allowfullscreen="" style="max-width: 100%"&gt;&lt;/iframe&gt;&lt;/div&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;What we covered&lt;/H2&gt;
&lt;P&gt;The session focused on four major areas:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The evolution of the Microsoft Copilot experience&lt;/LI&gt;
&lt;LI&gt;The roles of &lt;STRONG&gt;Home, Code and Autopilot&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Microsoft Copilot Managed Runtime and enterprise governance&lt;/LI&gt;
&lt;LI&gt;Usage-based AI and the emerging discipline of &lt;STRONG&gt;FinOps for AI&lt;/STRONG&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Together, these capabilities point toward a Copilot experience that extends beyond conversational assistance and toward increasingly sophisticated AI-enabled work.&lt;/P&gt;
&lt;H2&gt;A new Microsoft Copilot experience&lt;/H2&gt;
&lt;P&gt;Microsoft has announced three major capabilities for the new Copilot experience: &lt;STRONG&gt;Home, Code and Autopilot&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Home&lt;/STRONG&gt; brings Chat and Cowork together as a starting point for work. Microsoft is also bringing Word, Excel and PowerPoint capabilities into the Copilot experience, making it possible to create and continue working with Office content without continually rebuilding context across applications.&lt;/P&gt;
&lt;P&gt;There is an important distinction between Chat and Cowork.&lt;/P&gt;
&lt;P&gt;Chat addresses the conversational interactions many people already associate with Copilot: asking questions, looking up information, creating drafts and staying informed.&lt;/P&gt;
&lt;P&gt;Cowork is designed for work you &lt;STRONG&gt;delegate&lt;/STRONG&gt;. Rather than simply responding to an individual prompt, Cowork can work through more complex tasks end-to-end and return results for you to review and iterate upon.&lt;/P&gt;
&lt;P&gt;Microsoft has also said that the experience is moving toward a point where users won't necessarily need to decide which mode to choose. Users will describe what they want to accomplish and Copilot can route the work to the appropriate capability.&lt;/P&gt;
&lt;P&gt;That reflects an important change in how we should think about AI at work. The conversation is expanding from &lt;EM&gt;“What can I ask Copilot?”&lt;/EM&gt; toward &lt;EM&gt;“What work can I accomplish with Copilot?”&lt;/EM&gt;&lt;/P&gt;
&lt;H2&gt;Code: turning ideas into working solutions&lt;/H2&gt;
&lt;P&gt;One of the capabilities we spent time discussing and demonstrating during the webinar was &lt;STRONG&gt;Code&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;Code is designed to enable people to build solutions by describing what they want to create. Microsoft says the capability is powered by the same underlying technology as GitHub Copilot and is intended to make software creation accessible to both experienced developers and people who may not consider themselves traditional programmers.&lt;/P&gt;
&lt;P&gt;During the webinar, we explored this concept through an application-building example based on a requirements document.&lt;/P&gt;
&lt;P&gt;The point wasn't that application development suddenly requires no planning or technical discipline. It was to demonstrate how dramatically the starting point can change when AI can help translate business requirements into working software.&lt;/P&gt;
&lt;P&gt;Watch the webinar recording to see the example and the resulting application.&lt;/P&gt;
&lt;H2&gt;Where does AI-generated code actually run?&lt;/H2&gt;
&lt;P&gt;Making application creation easier immediately raises another question:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;How does an organization govern all of those applications?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Microsoft Copilot Managed Runtime is designed to address that challenge.&lt;/P&gt;
&lt;P&gt;Microsoft describes Managed Runtime as an enterprise-grade platform for running code within the Microsoft 365 tenant boundary. It provides a common foundation incorporating Microsoft-operated cloud hosting, identity, governed data access and lifecycle management.&lt;/P&gt;
&lt;P&gt;Managed Runtime already supports apps created through Copilot Cowork, Copilot Code and Microsoft Copilot Studio.&lt;/P&gt;
&lt;P&gt;This creates an important separation between two ideas:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;AI makes building easier. Enterprise controls still matter when that software runs.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Microsoft operates the platform, while organizations retain control over the boundaries within which applications operate.&lt;/P&gt;
&lt;H2&gt;Autopilot: AI that continues working&lt;/H2&gt;
&lt;P&gt;The webinar also explored &lt;STRONG&gt;Autopilot&lt;/STRONG&gt;, which Microsoft describes as a persistent, proactive and personal agent that can continue working even when the user isn't actively interacting with it.&lt;/P&gt;
&lt;P&gt;This represents another shift in the AI experience.&lt;/P&gt;
&lt;P&gt;Chat is naturally interactive. You ask something and Copilot responds.&lt;/P&gt;
&lt;P&gt;Agentic experiences introduce the idea of delegating work that can continue beyond that individual interaction. That opens new possibilities for ongoing research, monitoring, preparation and other work that benefits from persistence.&lt;/P&gt;
&lt;P&gt;In the webinar, we discussed what this transition could mean for people who increasingly treat AI not simply as a place to ask questions, but as another resource available to help them get work done.&lt;/P&gt;
&lt;H2&gt;As AI becomes more capable, cost management matters too&lt;/H2&gt;
&lt;P&gt;More capable AI workloads can also require different approaches to licensing and consumption.&lt;/P&gt;
&lt;P&gt;Microsoft uses &lt;STRONG&gt;Copilot Credits&lt;/STRONG&gt; as a common currency for eligible services using usage-based billing. Microsoft describes this consumption model as complementary to fixed subscription licensing, especially as more advanced or multi-step workloads can vary considerably in the amount of work required to complete a task.&lt;/P&gt;
&lt;P&gt;That leads directly to another major subject from our webinar: &lt;STRONG&gt;FinOps for AI&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;As organizations expand their use of AI, several questions become increasingly important:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;What are we consuming?&lt;/LI&gt;
&lt;LI&gt;Which services and scenarios are driving that consumption?&lt;/LI&gt;
&lt;LI&gt;What value are those scenarios creating?&lt;/LI&gt;
&lt;LI&gt;Where should we invest or optimize next?&lt;/LI&gt;
&lt;/UL&gt;
&lt;H2&gt;Control, measure and optimize&lt;/H2&gt;
&lt;P&gt;A useful way to think about FinOps for AI is through three activities:&lt;/P&gt;
&lt;H3&gt;Control&lt;/H3&gt;
&lt;P&gt;Organizations need mechanisms for governing access and spend.&lt;/P&gt;
&lt;P&gt;Microsoft's Cost Management capabilities support controls around usage-based AI experiences, including spending policies, limits, alerts and billing methods.&lt;/P&gt;
&lt;P&gt;Organizations can therefore begin establishing guardrails around how consumption-based AI services are introduced.&lt;/P&gt;
&lt;H3&gt;Measure&lt;/H3&gt;
&lt;P&gt;You can't optimize what you can't see.&lt;/P&gt;
&lt;P&gt;Microsoft provides consumption information through its Copilot Cost Management capabilities, giving administrators visibility into Copilot Credit consumption across supported services.&lt;/P&gt;
&lt;P&gt;This moves the AI cost conversation beyond simply purchasing technology and toward understanding how it is actually being consumed.&lt;/P&gt;
&lt;H3&gt;Optimize&lt;/H3&gt;
&lt;P&gt;Once organizations understand consumption, they can make more deliberate decisions about where AI is producing meaningful value and where different approaches may be appropriate.&lt;/P&gt;
&lt;P&gt;That makes FinOps for AI more than a billing conversation. It becomes part of the broader process of deciding where and how an organization wants to scale AI.&lt;/P&gt;
&lt;H2&gt;A useful way to think about what comes next&lt;/H2&gt;
&lt;P&gt;Perhaps the biggest takeaway from the webinar is that Microsoft Copilot is expanding beyond a single conversational interaction model.&lt;/P&gt;
&lt;P&gt;The emerging experience spans several ways of working:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Ask&lt;/STRONG&gt; when you need information or immediate assistance.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Delegate&lt;/STRONG&gt; when you want AI to take on a more complex body of work.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Build&lt;/STRONG&gt; when you want to turn an idea or requirement into a solution.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Automate&lt;/STRONG&gt; when work should continue beyond the immediate conversation.&lt;/P&gt;
&lt;P&gt;And surrounding those experiences are the governance and cost-management capabilities organizations need as AI adoption grows.&lt;/P&gt;
&lt;H2&gt;Watch the full webinar&lt;/H2&gt;
&lt;P&gt;We've only touched on the highlights here.&lt;/P&gt;
&lt;P&gt;In the full webinar, we walk through the new Copilot experience, demonstrate application creation with Code, discuss Autopilot and Managed Runtime, and spend additional time looking at the emerging FinOps capabilities organizations can use to understand and govern AI consumption.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Watch the accompanying video for the complete discussion and demonstrations.&lt;/STRONG&gt;&lt;/P&gt;
&lt;H2&gt;Learn more&lt;/H2&gt;
&lt;P&gt;Want to explore these announcements and capabilities in more detail?&lt;/P&gt;
&lt;P&gt;Check out these official Microsoft resources:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://blogs.microsoft.com/blog/2026/09/25/introducing-the-new-copilot-with-home-code-and-autopilot/" target="_blank" rel="noopener"&gt;Introducing the new Copilot with Home, Code and Autopilot&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://www.microsoft.com/en-us/copilot/blog/copilot-studio/build-where-you-want-run-with-confidence-now-microsoft-hosts-and-manages-the-code-created-by-copilot/" target="_blank" rel="noopener"&gt;Microsoft Copilot Managed Runtime: Build where you want, run with confidence&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://learn.microsoft.com/en-us/microsoft-365/copilot/usage-based-billing-overview-copilot-credits" target="_blank" rel="noopener"&gt;Usage-based billing and cost management for Copilot Credits&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://www.microsoft.com/licensing/guidance/Copilot-Credits" target="_blank" rel="noopener"&gt;Microsoft Copilot Credits licensing guidance&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/bade/documents/products-and-services/en-us/ai/Copilot-Credits-Guide.pdf" target="_blank" rel="noopener"&gt;Copilot Credits Guide&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Mon, 12 Oct 2026 19:47:32 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/the-new-microsoft-copilot/ba-p/4563898</guid>
      <dc:creator>NicholasAquino</dc:creator>
      <dc:date>2026-10-12T19:47:32Z</dc:date>
    </item>
    <item>
      <title>The Questions Never Change</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/the-questions-never-change/ba-p/4561652</link>
      <description>&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;AI agent governance becomes complicated when the conversation begins with technology: models, prompts, grounding, orchestration, autonomy, connectors, copilots, tools, and increasingly sophisticated ways for software to act on our behalf. But the technology is new; the governance questions are not.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;All of that matters, but there's another way to look at the problem. Strip away the AI terminology for a moment and ask the questions enterprise IT has always asked when a new asset class enters the environment.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="6" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What do I have?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="6" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Who is accountable for it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="6" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What can it reach?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="6" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What is it actually doing?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="6" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;How does it go away?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Those questions haven’t changed; only the subject has. Together, they form a six-question governance framework for agents: inventory, accountability, access, observation, protection, and retirement.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335559685&amp;quot;:0}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;What do I have?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Every governance program starts with visibility. You can't govern what you can't see.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="7" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;For people, organizations built directories and identity inventories.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="7" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;For devices, they built management and inventory systems.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="7" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;For applications, they built application catalogs and registration processes.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="7" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;For data, they built classification, discovery and information governance capabilities.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Now we're facing the same fundamental question with agents: What agents exist in my environment? Not just the ones IT knows about, and not just the ones that went through a formal project. The actual population.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="8" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What was built?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="8" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Who built it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="8" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What is it called?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="8" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Where does it run?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="8" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What is it connected to?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This is why I think &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;agent inventory is the first control, not an administrative exercise&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;. Before an agent can be secured, owned, scoped, observed, or retired, the organization must know it exists. Inventory is what makes every later governance control possible.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;Who is accountable for it?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Inventory tells you &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;what&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt; exists, it doesn't tell you who is responsible. That's the second question we've asked across every enterprise asset class: Who owns this?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="9" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;With a person, accountability may sit with a manager.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="9" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;With a device, there may be a primary user or assigned administrator.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="9" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;With an application, there's typically a business or technical owner.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="9" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;With data, ownership may sit with a business function or information owner.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Agents need the same clarity. Accountability should not rest only with the technical creator or the person who happened to build the workflow. Every agent needs a named sponsor and a named owner.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That's an important distinction. The person who builds an agent today may not be the person responsible for its business outcome six months from now. If nobody owns the agent, nobody is accountable for deciding whether it should continue to exist. And that becomes particularly important when the agent is no longer experimental. It has become part of your infrastructure.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;What can it reach?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This is where agent governance starts to intersect directly with security. Every asset has a scope.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="10" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;A user has permissions.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="10" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;A device has policies.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="10" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;An application has delegated access.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="10" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Data has access controls.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;So, the question for an agent is straightforward: What can this thing reach?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="11" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Which applications?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="11" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Which sites?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="11" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Which files?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="11" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Which mail?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="11" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Which systems?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="11" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="6" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Which identities?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;And perhaps most importantly: Does it need all of that access?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This is where least privilege becomes more than a security principle. It becomes an agent design principle. The goal isn't to make an agent powerful enough to do everything. It's to make it capable of doing what it is supposed to do—and no more.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That probably sounds familiar, because it is. We've been solving this problem for identities and applications for years. The subject has changed, the question hasn't.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;What is it actually doing?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Inventory tells us what exists; ownership tells us who is accountable, and access controls tell us what an agent &lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;can&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt; do. But there's another question every operations and security team eventually asks: What is it actually doing?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This is where observation matters. A static permission assignment only tells you what an agent could reach. It doesn't necessarily tell you what it does with that access. So agent governance needs visibility into usage and activity.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="12" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Which agents are active?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="12" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What are they connected to?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="12" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;How are those connections being used?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="12" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Are their behaviors consistent with their intended purpose?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="12" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Are there security signals that require investigation?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This is the move from simple inventory toward an &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;agent map and usage insights&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt;. Inventory identifies which agents exist. An agent map reveals their relationships and dependencies. Usage insights show how those connections are actually being used.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That's an important shift because an inventory answers: What do we have? An agent map starts answering: What is this connected to? And telemetry begins answering: What is it doing?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Those are different questions, and you need all three.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;How does it go away?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This may be the least glamorous question in technology, but it may also be one of the most important. How does it go away?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="13" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;We've built employee offboarding.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="13" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;We've built device retirement.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="13" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;We've built application decommissioning.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="13" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;We've built data retention and disposal processes.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Agents need an exit strategy too.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="14" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What happens when the business process changes?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="14" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What happens when the owner leaves?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="14" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What happens when the underlying data changes?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="14" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What happens when an agent is replaced?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="14" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What happens when nobody uses it anymore?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;An agent shouldn't remain in the environment simply because nobody remembered to retire it. A lifecycle isn't complete until it has a defined ending. Creation without retirement becomes accumulation, and accumulation becomes governance sprawl.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The first five questions establish whether an agent is known, owned, appropriately scoped, observable, and removable. A sixth question connects those controls to the security and data governance foundations beneath the agent: &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;How do I keep it from hurting me?&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This sixth question is addressed through two complementary disciplines. Threat detection identifies harmful or anomalous agent activity. Data protection safeguards the information agents read, generate, and send. Together, they extend governance beyond the agent itself to the underlying control plane and operating environment.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134233117&amp;quot;:false,&amp;quot;134233118&amp;quot;:false,&amp;quot;201341983&amp;quot;:0,&amp;quot;335551550&amp;quot;:1,&amp;quot;335551620&amp;quot;:1,&amp;quot;335559685&amp;quot;:0,&amp;quot;335559737&amp;quot;:0,&amp;quot;335559738&amp;quot;:0,&amp;quot;335559739&amp;quot;:160,&amp;quot;335559740&amp;quot;:278}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;An agent may be perfectly identified, it may have an owner, its permissions may be scoped, its activity may be observable, and it may even have a retirement process. But if the information it can access is poorly governed, the organization still has a problem.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Which brings us back to something from the &lt;A class="lia-internal-link lia-internal-url lia-internal-url-content-type-blog" href="https://techcommunity.microsoft.com/blog/HealthcareAndLifeSciencesBlog/the-fifth-lifecycle-ai-agents-are-the-new-enterprise-asset-class/4559961" target="_blank" rel="noopener" data-lia-auto-title="first article" data-lia-auto-title-active="0"&gt;first article&lt;/A&gt;: The agent lifecycle depends on the lifecycles underneath it, same questions and the same control plane.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This is why I don't think organizations need to invent an entirely new philosophy for agent governance. They need to extend the one they've already developed. The vocabulary might look different: Agent registry. Agent identity. Least privilege. Agent map. Usage insights. Lifecycle workflows.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;But the underlying disciplines are familiar.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV class="styles_lia-table-wrapper__h6Xo9 styles_table-responsive__MW0lN"&gt;&lt;table border="1" style="border-width: 1px;"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;The question&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;The governance objective&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;What do I have?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Inventory&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Who owns it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Accountability&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;What can it reach?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Scope and least privilege&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;What is it doing?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Observation&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;How do I protect it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Security and data protection&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;How does it go away?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Lifecycle and retirement&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;colgroup&gt;&lt;col style="width: 50.00%" /&gt;&lt;col style="width: 50.00%" /&gt;&lt;/colgroup&gt;&lt;/table&gt;&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;BR /&gt;&lt;SPAN data-contrast="auto"&gt;That's the fifth lifecycle. Agents aren't identical to users, devices, applications, or data; they introduce new characteristics and operational considerations. But they belong in the same enterprise governance conversation: they must be known, owned, controlled, observed, protected, and eventually retired. The mistake is treating every agent as an exception.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;There's a temptation with new technology to create an entirely separate governance universe.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="15" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;A new committee.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="15" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;A new policy.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="15" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;A new vocabulary.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="15" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;A new process.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="15" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;A new dashboard.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Maybe some of that will ultimately be necessary, but I'd start somewhere simpler. Take the questions your organization already knows how to ask and apply them to agents, then identify where the existing controls are not sufficient.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That changes the conversation. Instead of asking, “How do we govern this completely new thing?” organizations can ask, “Which parts of our existing governance model already work, and where do agents require something different?”&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That's a much more useful starting point because the objective isn't to make agents fit yesterday's technology; it's to make sure tomorrow's technology doesn't escape the disciplines we've already learned. The questions never change.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="16" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What do I have?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="16" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Who is accountable for it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="16" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What can it reach?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="16" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What is it actually doing?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="16" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;How do I protect it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="16" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="6" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;How does it go away?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;We've asked these questions of every major enterprise asset class. Agents may be the fifth, but the most important lesson comes from the first four: Governance doesn't begin when something goes wrong. It begins when you can answer the questions.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt;Inventory it. &lt;/SPAN&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt;Identify&lt;/SPAN&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt; it. Own it. Scope it. Watch it. Retire it.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The subject is new; the questions aren't.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;SPAN data-contrast="auto"&gt;This is the second article in a series exploring the "fifth lifecycle" of enterprise IT: the governance of AI agents alongside identity, devices, applications and data.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Oct 2026 14:28:19 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/the-questions-never-change/ba-p/4561652</guid>
      <dc:creator>Chad Stout</dc:creator>
      <dc:date>2026-10-05T14:28:19Z</dc:date>
    </item>
    <item>
      <title>The Fifth Lifecycle: AI Agents Are the New Enterprise Asset Class</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/the-fifth-lifecycle-ai-agents-are-the-new-enterprise-asset-class/ba-p/4559961</link>
      <description>&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Every so often, IT encounters a new kind of actor inside the enterprise. The pattern is familiar: adoption outpaces governance, inventory lags behind use, ownership remains unclear and access accumulates. Security teams ask what the technology can reach and who is accountable. Eventually, IT builds a lifecycle around it.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;We've lived through this before.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;In the 1990s, the new actor was &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;identity&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;In the 2000s, it was &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;devices&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;In the 2010s, it was &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;applications&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;In the 2020s, it became &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;data&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Now we're entering the fifth era: &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;AI agents&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt;.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;And I think that's an important way to think about the governance challenge in front of us. Not as an entirely new problem, but as the fifth enterprise asset class.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This article explains why agents fit a lifecycle pattern IT already understands, what makes them different from earlier asset classes, and why inventory is the practical first step toward responsible governance.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;The questions haven't changed&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;When a new technology enters the enterprise, IT eventually has to answer the same fundamental questions:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What do we have?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Who is accountable for it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What can it reach?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What is it actually doing?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;How do we protect it?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="1" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="6" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;How does it go away?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;We asked those questions about employees and their identities. We asked them about laptops and mobile devices. We asked them about applications—especially the ones that appeared outside traditional IT processes. We asked them about data as information spread across sites, mailboxes, endpoints and cloud services. And now we need to ask them about agents. The subject has changed. &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;The control problem hasn't&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;Every new asset class starts unmanaged&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Think about what happened in each of the previous eras.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Identity management evolved from basic domain accounts into directory services and modern identity platforms. The lifecycle became something everyone in IT understood:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt;Join. Move. Leave.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Device management followed a similar path:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt;Enroll. Configure. Prove compliance. Patch. Wipe. Retire.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Applications introduced another set of governance questions:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt;Discover. Register. Scope consent. Review. Decommission.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Then came data. As information proliferated across Microsoft 365, SharePoint, mailboxes and endpoints, organizations had to develop ways to:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt;Classify. Protect. Retain. Audit. Dispose.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Different technology. Different tools. Different risks. But underneath them was the same organizational muscle:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;Inventory it. Give it an identity. Assign an owner. Define its scope. Observe it. Secure it. Retire it.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;We've built this muscle four times. Agents are the fifth.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;The difference is that agents act&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;There is, however, something important about this fifth asset class. An agent isn't just something sitting in the environment waiting for a human to interact with it. It can reason across information, invoke applications, retrieve data, and take actions on someone's behalf. That changes the consequences of poor governance.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;An employee with excessive access is a problem. An application with excessive permissions is a problem. An overshared repository is a problem. An agent operating across those systems can compound all three: it can surface exposed information faster, connect it across sources, and act on it at scale. The agent may not create the underlying permission problem, but it can dramatically increase the problem’s reach and operational impact.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That's why agent governance can't be separated from the governance disciplines that came before it.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;The uncomfortable truth: your data matters more than your model&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;This may be one of the most important ideas in agent governance. An agent isn't useful simply because of the model behind it. It's useful because of &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;what it is allowed to see and do&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Consider a simple example:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;An employee asks an agent a question. The agent is grounded in information from a SharePoint site or another enterprise knowledge source. If that employee already has access to the underlying information, the agent can work with it in that user's context.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The agent didn't necessarily grant the employee new access. It reflected the access that was already there. That sounds reassuring, until you realize what it means.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;If the organization has years of stale documents, poorly governed sites, excessive permissions, unclear ownership and sensitive information that was never properly classified, the agent may expose those weaknesses much faster than a human ever could.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;For years, an overshared document could remain effectively hidden because nobody knew it existed. Now someone can simply ask a question.&lt;STRONG&gt; &lt;/STRONG&gt;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;The permission didn't change. The obscurity did.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-contrast="auto"&gt; Agents make existing information easier to discover, which means the agent lifecycle depends directly on the data lifecycle.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;If your content has no lifecycle, &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;your agent inherits the absence of one.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;Governance should enable adoption, not block it&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Agent adoption creates a familiar tension: business teams want to build, while IT and security teams need visibility into what agents can access and do. Those objectives do not have to conflict.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;We've seen this movie before with devices and applications. Bring-your-own-device programs didn't eliminate the need for device management. Shadow IT didn't eliminate the need for application governance. Instead, organizations eventually developed ways to discover what existed, establish ownership, control access and manage the lifecycle.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Agents will require the same evolution.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The goal shouldn't be to create a governance process so cumbersome that nobody can build an agent. Nor should the goal be to let an uncontrolled population of agents grow indefinitely. The goal is to make &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;responsible agent adoption operationally possible&lt;/SPAN&gt;&lt;SPAN data-contrast="auto"&gt;.&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;That starts with visibility.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;Start with inventory, not policy&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;One of the easiest mistakes an organization can make is beginning the agent conversation with a policy question. A more useful starting point is visibility: before deciding what the policy should be, establish what agents already exist and how they are connected.&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Who built them?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Who owns them?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What are they connected to?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="6" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What data can they reach?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="7" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What identities do they use?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="8" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What are they doing?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="9" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Which ones are still needed?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="2" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="10" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Which ones have effectively become digital orphans?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;You may discover that the agent population is already larger than anyone in the room expected. That number is more than an inventory statistic: it reveals the scale of unmanaged ownership, access, connections and lifecycle risk. It gives leaders a concrete starting point for prioritizing governance resources and controls—and a business case grounded in what already exists.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H3 aria-level="2"&gt;&lt;SPAN data-contrast="none"&gt;&lt;SPAN data-ccp-parastyle="heading 2"&gt;The fifth lifecycle&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;134245418&amp;quot;:true,&amp;quot;134245529&amp;quot;:true,&amp;quot;335559738&amp;quot;:160,&amp;quot;335559739&amp;quot;:80}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The good news is that we don't have to invent this from scratch. The emerging agent lifecycle is remarkably familiar:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt;Register. Identify. Sponsor. Scope. Observe. Secure. Retire.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The technology supporting those controls will continue to evolve. Platforms will change. Agent architectures will change. The way agents interact with applications and data will change. But the organizational questions are likely to remain remarkably stable.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="3" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="1" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;Who owns this?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="3" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="2" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What can it do?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="3" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="3" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;What can it see?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="3" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="4" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;How do we know what it's doing?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI aria-setsize="-1" data-leveltext="" data-font="Symbol" data-listid="3" data-list-defn-props="{&amp;quot;335552541&amp;quot;:1,&amp;quot;335559685&amp;quot;:720,&amp;quot;335559991&amp;quot;:360,&amp;quot;469769226&amp;quot;:&amp;quot;Symbol&amp;quot;,&amp;quot;469769242&amp;quot;:[8226],&amp;quot;469777803&amp;quot;:&amp;quot;left&amp;quot;,&amp;quot;469777804&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;469777815&amp;quot;:&amp;quot;hybridMultilevel&amp;quot;}" data-aria-posinset="5" data-aria-level="1"&gt;&lt;SPAN data-contrast="auto"&gt;How do we know when it should stop?&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Those are not AI questions. They're enterprise governance questions. And that's the mindset shift I think organizations need to make.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;AI agents may feel unprecedented, but the governance pattern is not. IT has repeatedly moved new classes of technology from unknown to inventoried, owned, controlled, observed and retired. Agents are the latest—and arguably the most consequential—addition to that lifecycle.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;The question, then, is not how to invent governance for AI agents. It is how to apply the governance discipline we have spent decades building to a fifth enterprise asset class. The pattern is familiar, and that makes the problem far more manageable.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;And it starts with a surprisingly simple first step:&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-align-center"&gt;&lt;STRONG&gt;&lt;SPAN data-contrast="auto"&gt;&lt;SPAN data-ccp-charstyle="Book Title"&gt;Inventory it.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{&amp;quot;335551550&amp;quot;:2,&amp;quot;335551620&amp;quot;:2}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN data-contrast="auto"&gt;Because before you can govern the agents you intend to build, you need to understand the agents that are already there.&lt;/SPAN&gt;&lt;SPAN data-ccp-props="{}"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;SPAN data-contrast="auto"&gt;This is the first article in a series exploring the fifth lifecycle of enterprise IT: governing AI agents alongside identities, devices, applications and data. The next articles will examine the controls organizations need to turn visibility into durable ownership, security, observability and responsible retirement practices.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2026 13:47:50 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/the-fifth-lifecycle-ai-agents-are-the-new-enterprise-asset-class/ba-p/4559961</guid>
      <dc:creator>Chad Stout</dc:creator>
      <dc:date>2026-09-30T13:47:50Z</dc:date>
    </item>
    <item>
      <title>HLS in Practice: September 2026</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/hls-in-practice-september-2026/ba-p/4559058</link>
      <description>&lt;P style="margin-bottom: 16px;"&gt;There’s plenty of Microsoft AI news. Figuring out which updates deserve your attention takes more work.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;This edition brings together practical reads from the Healthcare and Life Sciences Blog and other Microsoft teams, covering everyday work, clinical workflows, business apps, and governance.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;EM&gt;Recent reading from August 24 through September 22, 2026. Availability reflects the sources available on September 22. Readiness items are labeled separately.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;In this edition&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;A href="#community--1-hls-reads" target="_blank"&gt;From the HLS blog&lt;/A&gt;: choosing Copilot or Cowork, clinical workflows, and meeting governance.&lt;/LI&gt;
&lt;LI&gt;&lt;A href="#community--1-microsoft-updates" target="_blank"&gt;Beyond the HLS blog&lt;/A&gt;: business apps, agent building, and life sciences examples.&lt;/LI&gt;
&lt;LI&gt;&lt;A href="#community--1-governance-watch" target="_blank"&gt;Governance watch&lt;/A&gt;: meeting-archive retention.&lt;/LI&gt;
&lt;LI&gt;&lt;A href="#community--1-try-this" target="_blank"&gt;One thing to try&lt;/A&gt;: brief a colleague on one update.&lt;/LI&gt;
&lt;/UL&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H2 id="hls-reads" style="color: #a0354d; margin-top: 32px; margin-bottom: 16px;"&gt;From the HLS blog&lt;/H2&gt;
&lt;H3 style="font-size: 24px; line-height: 1.3; margin-top: 24px; margin-bottom: 10px;"&gt;Choose between Copilot and Copilot Cowork&lt;/H3&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; business leaders and operations teams&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;In a September 10 article, Nick (NicholasAquino) compares everyday work you guide step by step with multistep tasks you delegate toward a defined outcome.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;Put it to work:&lt;/STRONG&gt; Start with a familiar task. Use Copilot to improve a project update; evaluate Cowork when preparing a recurring briefing requires gathering several approved sources. Confirm access, permissions, review points, and usage-based costs before delegating actions.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;A href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/copilot-or-copilot-cowork---which-tool-to-use---and-when/4555402" target="_blank"&gt;Read: Copilot or Copilot Cowork, which tool to use and when&lt;/A&gt;&lt;BR /&gt;&lt;EM&gt;Nick (NicholasAquino) | HLS Blog, September 10, 2026. Practical selection guidance, not a new product launch.&lt;/EM&gt;&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H3 style="font-size: 24px; line-height: 1.3; margin-top: 24px; margin-bottom: 10px;"&gt;Explore AI assistance where clinicians already work&lt;/H3&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; clinical leaders and informatics teams&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;In a September 9 article, sarahgrey explores Dragon Copilot’s focus capability, which brings assistance into the text field where a clinician is working. The examples include reviewing selected information and drafting or refining text without moving everything into a separate application.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;The useful starting point is a workflow discussion. Where does your team repeatedly copy information between applications, reformat documentation, or recreate the same type of document?&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;Put it to work: &lt;/STRONG&gt;Choose one example to review with your clinical informatics team. Confirm the capabilities available in your environment and the required clinical review before using patient information.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;A href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/ai-where-and-when-you-need-it-with-dragon-copilots-ability-to-focus/4554293" target="_blank"&gt;Read: AI where and when you need it with Dragon Copilot’s ability to focus&lt;/A&gt;&lt;BR /&gt;&lt;EM&gt;sarahgrey | HLS Blog, September 9, 2026. Availability and deployment requirements should be confirmed for your organization.&lt;/EM&gt;&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H3 style="font-size: 24px; line-height: 1.3; margin-top: 24px; margin-bottom: 10px;"&gt;Review what your AI-assisted meetings leave behind&lt;/H3&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; meeting organizers, privacy teams, and Microsoft 365 administrators&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;On September 3, Michael Goad published a walkthrough of using Copilot only during a Teams meeting without creating a saved transcript.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;The governance question extends beyond the recording button. Copilot prompts and responses may still be retained for compliance purposes, depending on your organization’s configuration. Shared notes and other meeting experiences also need their own review.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;Put it to work: &lt;/STRONG&gt;Before changing meeting policies, bring your privacy, records-management, and IT teams together around one meeting scenario. Decide what information should persist, who should have access, and which experiences are appropriate.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;A href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/using-copilot-in-sensitive-healthcare-teams-meetings---without-recording-or-tran/4553097" target="_blank"&gt;Read: Using Copilot in Sensitive Healthcare Teams Meetings&lt;/A&gt;&lt;BR /&gt;&lt;EM&gt;Michael Goad | HLS Blog, September 3, 2026. An existing-capability walkthrough, not a new feature announcement.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;A href="https://learn.microsoft.com/en-us/microsoftteams/copilot-teams-transcription" target="_blank"&gt;Current Microsoft guidance on Copilot and meeting transcription&lt;/A&gt;&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H2 id="microsoft-updates" style="color: #a0354d; margin-top: 32px; margin-bottom: 16px;"&gt;Beyond the HLS blog&lt;/H2&gt;
&lt;H3 style="font-size: 24px; line-height: 1.3; margin-top: 24px; margin-bottom: 10px;"&gt;Describe a business app, then review what it builds&lt;/H3&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; operations teams, makers, and IT administrators&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;On September 10, Ryan Cunningham announced app building in Copilot Studio, with public preview rolling out. The same announcement introduced an &lt;CODE&gt;/app&lt;/CODE&gt; skill in Copilot Cowork through the Frontier program.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;The experience lets you describe an application, review a working preview, and refine it through conversation. Apps can connect to business systems, which makes access and write permissions part of the discussion from the beginning.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;Put it to work: &lt;/STRONG&gt;A staff-onboarding tracker using fictional records could be a useful first exploration. Define who would use it, what they should see, and which changes they should be allowed to make. Have the appropriate technical owner review the generated application before connecting real organizational data.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;Availability:&lt;/STRONG&gt; Copilot Studio public preview; the Cowork route is through Frontier. Confirm access in your environment. Building and running apps follows usage-based billing.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;A href="https://www.microsoft.com/en-us/copilot/blog/copilot-studio/build-apps-in-copilot-cowork-and-copilot-studio/" target="_blank"&gt;Read: Build apps in Copilot Cowork and Copilot Studio&lt;/A&gt;&lt;BR /&gt;&lt;EM&gt;Ryan Cunningham | Microsoft Copilot Blog, September 10, 2026.&lt;/EM&gt;&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H3 style="font-size: 24px; line-height: 1.3; margin-top: 24px; margin-bottom: 10px;"&gt;Understand what GitHub Copilot brings to Copilot Studio&lt;/H3&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; agent builders and the teams funding their work&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;Jason Moore’s September 2 update explains the GitHub Copilot harness in Copilot Studio. A harness coordinates how an agent uses a model, context, and tools to complete a task.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;This is more than connecting a GitHub repository. It gives builders another foundation for agents that reason through multistep business processes, alongside Copilot Studio’s standard harness.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;Put it to work: &lt;/STRONG&gt;For HLS operations, consider a nonclinical example: reviewing fictional purchase orders and invoices, identifying mismatches, and routing exceptions to a person for approval.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;Availability:&lt;/STRONG&gt; The underlying harness reached general availability in August. This is September guidance on how to use it, not a September launch. Related capabilities can have separate preview statuses.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;Before building:&lt;/STRONG&gt; Review capacity and spending controls. Microsoft documents that building, testing, evaluating, and running these agents can consume Copilot Credits; that usage is not included with a user’s Microsoft 365 Copilot license.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;A href="https://www.microsoft.com/en-us/copilot/blog/copilot-studio/new-and-improved-github-copilot-harness-agent-skills-and-richer-context/" target="_blank"&gt;Read: GitHub Copilot harness, agent skills, and richer context&lt;/A&gt;&lt;BR /&gt;&lt;EM&gt;Jason Moore | Microsoft Copilot Blog, September 2, 2026.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;A href="https://learn.microsoft.com/en-us/power-platform/admin/manage-usage-github-copilot-harness" target="_blank"&gt;Review the current cost-management guidance&lt;/A&gt;&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H3 style="font-size: 24px; line-height: 1.3; margin-top: 24px; margin-bottom: 10px;"&gt;A life sciences read: AI across research and operations&lt;/H3&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; research, manufacturing, and life sciences teams&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;Jonathon Dreyer’s September 14 industry article looks at how pharmaceutical organizations apply AI across research, manufacturing, and operations.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;Put it to work:&lt;/STRONG&gt; Select one example and identify the information sources, scientific expertise, and validation your organization would need to explore it. These customer examples are not a promise that another organization will achieve the same results.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;A href="https://www.microsoft.com/en-us/microsoft-cloud/blog/healthcare/2026/09/14/the-ai-shift-is-real-how-pharmaceutical-leaders-are-operationalizing-ai/" target="_blank"&gt;Read: How pharmaceutical leaders are operationalizing AI&lt;/A&gt;&lt;BR /&gt;&lt;EM&gt;Jonathon Dreyer | Microsoft Cloud Blog, September 14, 2026. Industry examples, not a product availability announcement.&lt;/EM&gt;&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H2 id="governance-watch" style="color: #a0354d; margin-top: 32px; margin-bottom: 16px;"&gt;Governance watch&lt;/H2&gt;
&lt;H3 style="font-size: 24px; line-height: 1.3; margin-top: 24px; margin-bottom: 10px;"&gt;Meeting archives need a separate retention conversation&lt;/H3&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; Teams administrators, privacy, and records-management teams&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;Microsoft’s public documentation describes AI-generated meeting archives that can preserve meeting insights for AI experiences. The documentation currently identifies this capability as &lt;STRONG&gt;preview for organizations in the Teams TAP program&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;One detail deserves attention: deleting or expiring a transcript does not automatically delete its AI archive. Archive expiration and applicable Microsoft Purview retention policies need their own review.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;STRONG&gt;Before rollout: &lt;/STRONG&gt;This is a readiness item, not a recommendation to enable the feature today. Review the documented creation conditions, access, retention, and deletion behavior. Confirm applicable rollout information in your organization’s Message Center before planning changes.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;A href="https://learn.microsoft.com/en-us/microsoftteams/ai-archive-teams-meetings" target="_blank"&gt;Read: AI Archives for Microsoft Teams Meetings&lt;/A&gt;&lt;BR /&gt;&lt;EM&gt;Supporting Microsoft Learn guidance, last updated July 27, 2026.&lt;/EM&gt;&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;&lt;A href="https://www.microsoft.com/microsoft-365/roadmap?id=558933" target="_blank"&gt;Follow Roadmap 558933&lt;/A&gt;&lt;BR /&gt;&lt;EM&gt;Roadmap entry updated September 21, 2026; currently in development. Future rollout timing is subject to change.&lt;/EM&gt;&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H2 id="try-this" style="color: #a0354d; margin-top: 32px; margin-bottom: 16px;"&gt;One thing to try&lt;/H2&gt;
&lt;H3 style="font-size: 24px; line-height: 1.3; margin-top: 24px; margin-bottom: 10px;"&gt;Prepare a short briefing on one update&lt;/H3&gt;
&lt;P style="margin-bottom: 16px;"&gt;Choose one of this edition’s public announcements. In your organization’s approved Copilot experience, try:&lt;/P&gt;
&lt;BLOCKQUOTE style="background-color: #fbf6f5; color: #242424; border: 1px solid #e9d4d8; padding: 16px 20px; margin: 20px 0;"&gt;
&lt;P style="margin-bottom: 16px;"&gt;I want to explain this Microsoft update to a healthcare operations manager who doesn’t follow AI news. Help me write a short briefing about what changed, one nonclinical task it might help with, and what we should check before trying it.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;Use this public announcement: [paste the announcement link].&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P style="margin-bottom: 16px;"&gt;Read the response alongside the source. Check whether Copilot preserved the availability status and whether its suggested use case is reasonable. If it couldn’t access the page, provide the relevant public excerpt.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;Then ask:&lt;/P&gt;
&lt;BLOCKQUOTE style="background-color: #fbf6f5; color: #242424; border: 1px solid #e9d4d8; padding: 16px 20px; margin: 20px 0;"&gt;
&lt;P style="margin-bottom: 16px;"&gt;Make this shorter and explain any technical terms.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P style="margin-bottom: 16px;"&gt;Use public material for this exercise, and review the briefing before sharing it.&lt;/P&gt;
&lt;P style="margin-bottom: 16px;"&gt;If you’re still finding your starting point, visit &lt;A href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/get-started-with-microsoft-ai-in-healthcare-and-life-sciences/4559028" target="_blank"&gt;Get Started with Microsoft AI in Healthcare and Life Sciences&lt;/A&gt; for a beginner exercise, learning paths, and governance resources.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Sep 2026 16:36:55 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/hls-in-practice-september-2026/ba-p/4559058</guid>
      <dc:creator>michaelgoad</dc:creator>
      <dc:date>2026-09-22T16:36:55Z</dc:date>
    </item>
    <item>
      <title>Get Started with Microsoft AI in Healthcare and Life Sciences</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/get-started-with-microsoft-ai-in-healthcare-and-life-sciences/ba-p/4559028</link>
      <description>&lt;P&gt;You don’t need to learn every AI tool before finding something useful to do with one. Start with a task you already understand: organizing notes, preparing a presentation, or finding information.&lt;/P&gt;
&lt;P&gt;This guide brings together practical examples, governance resources, and learning materials from the HLS blog and other Microsoft teams. If you’re new to AI, begin with the exercise below. If you’re responsible for a rollout, head to the governance section.&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Resource guide updated September 22, 2026.&lt;/EM&gt;&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H2&gt;Before you start: know your organization’s guardrails&lt;/H2&gt;
&lt;P&gt;Use the tools and accounts your organization approves. Before bringing work information into an AI experience, confirm:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Permitted data:&lt;/STRONG&gt; What can you enter, upload, or connect?&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Access:&lt;/STRONG&gt; Who can use the tool and see the information involved?&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Human review:&lt;/STRONG&gt; Who checks the output before someone relies on it?&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Ownership:&lt;/STRONG&gt; Who handles questions, problems, and changes to a shared workflow?&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;For learning, start with public or fictional information. Patient information, unpublished research, and other sensitive data require approval for the specific tool and use case. A product setting alone does not establish compliance.&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H2&gt;Try your first task: turn rough notes into a follow-up email&lt;/H2&gt;
&lt;P&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; Anyone getting started.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;What you need:&lt;/STRONG&gt; Access to your organization’s approved Copilot Chat experience. Microsoft’s &lt;A href="https://learn.microsoft.com/copilot/overview" target="_blank" rel="noopener noreferrer"&gt;Copilot Chat overview&lt;/A&gt; explains access and eligibility. Features can differ by license, application, and tenant configuration.&lt;/P&gt;
&lt;P&gt;Imagine you’re helping your team put together a welcome guide for new employees. You’ve had a planning meeting and need to send everyone a quick recap. You have a few notes, but haven’t written the email.&lt;/P&gt;
&lt;P&gt;This example uses fictional people and information. Open your approved Copilot Chat experience with your work account and copy the whole prompt below, including the notes.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Try this:&lt;/STRONG&gt;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;I’m helping put together a welcome guide for new employees on our healthcare operations team. Turn these notes into a short, friendly follow-up email to the project team. Make it clear what everyone needs to do next.&lt;/P&gt;
&lt;P&gt;Notes: Jordan will draft the welcome guide by Friday. Priya will review it next week. We still need a volunteer to organize an orientation meeting, and we haven’t picked a date for that meeting.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Read the draft alongside the notes. Check that Jordan and Priya have the right tasks and timing. The volunteer and orientation date should still be undecided. Correct anything Copilot adds that the notes don’t support.&lt;/P&gt;
&lt;P&gt;Then continue in the same chat with a simple follow-up:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;Make it shorter and put the next steps in bullets.&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Keep this as a practice draft. The point is to ask for help with a familiar task, check the result, and tell Copilot what you want changed.&lt;/P&gt;
&lt;P&gt;For more examples, see Microsoft’s &lt;A href="https://support.microsoft.com/en-us/microsoft-365-copilot/get-better-copilot-responses-with-great-prompting" target="_blank" rel="noopener noreferrer"&gt;guide to getting better responses with prompting&lt;/A&gt;.&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H2&gt;Make reviewing the answer a habit&lt;/H2&gt;
&lt;P&gt;Before sharing or acting on AI-generated content:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Compare names, dates, numbers, and commitments with the source.&lt;/LI&gt;
&lt;LI&gt;Look for missing information and statements the source doesn’t support.&lt;/LI&gt;
&lt;LI&gt;Open citations and confirm they support the claim.&lt;/LI&gt;
&lt;LI&gt;Apply the human-review requirements for your work.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;An answer that reads well can still be wrong. When you assess whether AI helped, include the time you spent reviewing and correcting it.&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H2&gt;Choose a path that fits your work&lt;/H2&gt;
&lt;H3&gt;Everyday work&lt;/H3&gt;
&lt;P&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; Business leaders, administrative teams, and operations staff.&lt;/P&gt;
&lt;P&gt;Once you’re comfortable with a basic task, choose something you repeat: a project update, a presentation, or a document you rebuild each month.&lt;/P&gt;
&lt;P&gt;Start with &lt;A href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/copilot-or-copilot-cowork---which-tool-to-use---and-when/4555402" target="_blank" rel="noopener"&gt;Copilot or Copilot Cowork: which tool to use, and when&lt;/A&gt; to explore different approaches to the work.&lt;/P&gt;
&lt;P&gt;For a more advanced exercise, follow &lt;A href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/how-to-set-up-copilot-skills-in-powerpoint-and-build-your-own/4548273" target="_blank" rel="noopener"&gt;How to Set Up Copilot Skills in PowerPoint&lt;/A&gt;. Check that your organization has enabled the required capabilities before following the walkthrough.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Your next step:&lt;/STRONG&gt; Choose one recurring task and practice with fictional or public content before moving to approved work information.&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H3&gt;Clinical workflows&lt;/H3&gt;
&lt;P&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; Clinicians, clinical leaders, and informatics teams.&lt;/P&gt;
&lt;P&gt;Explore &lt;A href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/ai-where-and-when-you-need-it-with-dragon-copilots-ability-to-focus/4554293" target="_blank" rel="noopener"&gt;Dragon Copilot’s focus capability&lt;/A&gt; for examples of assistance within the applications where clinicians work.&lt;/P&gt;
&lt;P&gt;Treat this as a workflow discussion first. Reading about a capability doesn’t mean your organization has deployed or approved it.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Your next step:&lt;/STRONG&gt; Identify one documentation task and discuss it with your clinical informatics team. Confirm availability, the approved environment, and clinical review requirements before trying it with patient information.&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H3&gt;Governance and responsible adoption&lt;/H3&gt;
&lt;P&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; IT administrators, security and privacy teams, compliance leaders, and people responsible for AI rollout.&lt;/P&gt;
&lt;P&gt;Start with &lt;A href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/copilot-governance-a-practical-guide-from-our-4%E2%80%91part-webinar-series/4469033" target="_blank" rel="noopener"&gt;our four-part Copilot governance guide&lt;/A&gt;, or &lt;A href="https://www.youtube.com/playlist?list=PLdkhFJc5w6-F-J9Os8IzyGy969USAMSIx" target="_blank" rel="noopener nofollow noreferrer"&gt;watch the session recordings&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;The series covers:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Admin-center foundations:&lt;/STRONG&gt; Access, agent creation, rollout ownership, and billing controls.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Copilot Studio and Power Platform:&lt;/STRONG&gt; Environments, connectors, data policies, and agent governance.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Microsoft Purview:&lt;/STRONG&gt; Information protection, sensitivity labels, auditing, and risk.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;SharePoint Advanced Management:&lt;/STRONG&gt; Oversharing, content ownership, access reviews, and lifecycle management.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;EM&gt;Recorded in 2025.&lt;/EM&gt; Use the series to understand the foundations, then consult current product documentation for configuration and licensing. Microsoft’s &lt;A href="https://learn.microsoft.com/microsoft-365/copilot/enterprise-data-protection" target="_blank" rel="noopener noreferrer"&gt;enterprise data protection guidance&lt;/A&gt; is one important reference.&lt;/P&gt;
&lt;P&gt;For an applied example, read &lt;A href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/using-copilot-in-sensitive-healthcare-teams-meetings---without-recording-or-tran/4553097" target="_blank" rel="noopener"&gt;Using Copilot in Sensitive Healthcare Teams Meetings&lt;/A&gt;. Discuss the scenario with your privacy, security, records-management, and IT teams before adopting it.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Your next step:&lt;/STRONG&gt; Document one proposed workflow’s owner, permitted data, access requirements, approval checkpoints, and monitoring needs. For agents or usage-based services, include a consumption owner and review process.&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H3&gt;Research and life sciences&lt;/H3&gt;
&lt;P&gt;&lt;STRONG&gt;For:&lt;/STRONG&gt; Researchers, life sciences leaders, and data teams.&lt;/P&gt;
&lt;P&gt;Explore &lt;A href="https://www.microsoft.com/en-us/microsoft-cloud/blog/healthcare/2026/09/14/the-ai-shift-is-real-how-pharmaceutical-leaders-are-operationalizing-ai/" target="_blank" rel="noopener noreferrer"&gt;how pharmaceutical leaders are putting AI into practice&lt;/A&gt; across research, manufacturing, and operations.&lt;/P&gt;
&lt;P&gt;These examples can help you identify possibilities. They aren’t instructions to reproduce a regulated workflow without validation.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Your next step:&lt;/STRONG&gt; Select one relevant example and identify the data, scientific expertise, validation, and approvals your organization would need to explore it.&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H2&gt;Learn more from Microsoft&lt;/H2&gt;
&lt;P&gt;Our HLS blog is one place to learn. These official sources cover developments and guidance we may not address here:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;&lt;A href="https://www.microsoft.com/en-us/copilot/blog/" target="_blank" rel="noopener noreferrer"&gt;Microsoft Copilot Blog&lt;/A&gt;:&lt;/STRONG&gt; Product announcements and examples across productivity, business processes, and agents.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;&lt;A href="https://www.microsoft.com/en-us/microsoft-cloud/blog/industry-healthcare/" target="_blank" rel="noopener noreferrer"&gt;Microsoft Cloud healthcare and life sciences perspectives&lt;/A&gt;:&lt;/STRONG&gt; Industry developments and customer examples across healthcare and life sciences.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;&lt;A href="https://www.microsoft.com/en-us/security/blog/" target="_blank" rel="noopener noreferrer"&gt;Microsoft Security Blog&lt;/A&gt;:&lt;/STRONG&gt; Security, data protection, and governance perspectives.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;&lt;A href="https://learn.microsoft.com/microsoft-365/copilot/release-notes" target="_blank" rel="noopener noreferrer"&gt;Copilot release notes&lt;/A&gt;&lt;/STRONG&gt; and &lt;STRONG&gt;&lt;A href="https://learn.microsoft.com/en-us/microsoft-copilot-studio/whats-new" target="_blank" rel="noopener noreferrer"&gt;Copilot Studio updates&lt;/A&gt;:&lt;/STRONG&gt; Product changes and release information.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;When reading an announcement, check its publication date, release status, requirements, and supported platforms. Preview, planned, and generally available features are different stages. Even released features can roll out gradually.&lt;/P&gt;
&lt;P&gt;Use the &lt;A href="https://www.microsoft.com/en-us/microsoft-365/roadmap" target="_blank" rel="noopener noreferrer"&gt;Microsoft 365 Roadmap&lt;/A&gt; for planning, rather than assuming a listed feature is available in your environment.&lt;/P&gt;
&lt;HR style="border: 0; border-top: 1px solid #dedede; margin: 28px 0;" /&gt;
&lt;H2&gt;Earlier training and recordings&lt;/H2&gt;
&lt;P&gt;The &lt;A href="https://techcommunity.microsoft.com/blog/healthcareandlifesciencesblog/microsoft-365-copilot-learning-series-on-demand/4386335" target="_blank" rel="noopener"&gt;Microsoft 365 Copilot Learning Series on-demand recordings&lt;/A&gt; remain available as a learning archive. Check current documentation before following older setup instructions.&lt;/P&gt;
&lt;P&gt;Choose one resource and one small, approved task. Try it, review the result, and decide what you would change before using it again.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Sep 2026 18:45:09 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/get-started-with-microsoft-ai-in-healthcare-and-life-sciences/ba-p/4559028</guid>
      <dc:creator>michaelgoad</dc:creator>
      <dc:date>2026-09-22T18:45:09Z</dc:date>
    </item>
    <item>
      <title>Copilot or Copilot Cowork - Which tool to use - and When</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/copilot-or-copilot-cowork-which-tool-to-use-and-when/ba-p/4555402</link>
      <description>&lt;DIV class="lia-embeded-content" contenteditable="false"&gt;&lt;IFRAME src="https://www.youtube.com/embed/Xv_01fXDtfA" width="100%" height="450" allowfullscreen="allowfullscreen" style="border: 0;" sandbox="allow-scripts allow-same-origin allow-forms"&gt;
&lt;/IFRAME&gt;&lt;/DIV&gt;
&lt;P&gt;&lt;STRONG&gt;Microsoft 365 Copilot vs Copilot Cowork: Choosing the Right AI for Work&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;As organizations expand their use of AI to improve productivity and automate business processes, understanding which tool to use—and when—is critical. Microsoft offers two complementary capabilities: Microsoft 365 Copilot and Copilot Cowork. While they both leverage AI to support work, they are designed for fundamentally different types of tasks.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Two Different Models of AI Assistance&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Microsoft 365 Copilot is designed as a day-to-day productivity assistant embedded within familiar Microsoft 365 applications such as Word, Excel, PowerPoint, Outlook, and Teams. It works alongside users in real time, helping them create, summarize, analyze, and refine content. The user remains in control of each interaction, guiding the AI step by step.&lt;/P&gt;
&lt;P&gt;Typical use cases include:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Drafting and improving documents&lt;/LI&gt;
&lt;LI&gt;Summarizing emails and meetings&lt;/LI&gt;
&lt;LI&gt;Preparing presentations&lt;/LI&gt;
&lt;LI&gt;Analyzing information across work content&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This model is optimized for frequent, interactive assistance where the user actively directs the workflow.&lt;/P&gt;
&lt;P&gt;Copilot Cowork, by contrast, is designed for execution-based workflows. Instead of responding one step at a time, users define a desired outcome, and Cowork independently plans and executes the necessary steps to complete the task. It can operate across multiple tools, gather information, and produce finished outputs such as documents, emails, or Teams posts.&lt;/P&gt;
&lt;P&gt;It is especially suited for:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Multi-step workflows&lt;/LI&gt;
&lt;LI&gt;Scheduled or recurring tasks&lt;/LI&gt;
&lt;LI&gt;Event-triggered processes (such as responding to incoming emails or messages)&lt;/LI&gt;
&lt;LI&gt;Longer-running automated business processes&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Key Difference: Interaction vs Execution&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;The primary distinction between the two lies in control and autonomy:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Microsoft 365 Copilot supports guided, interactive work where the user drives each step.&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI&gt;Copilot Cowork executes defined workflows end-to-end with minimal intervention, pausing only for approvals when needed.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;In short:&lt;/P&gt;
&lt;P&gt;Copilot = assist in doing the work&lt;/P&gt;
&lt;P&gt;Cowork = do the work&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Pricing and Usage Model&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;The two systems also differ in how they are consumed:&lt;/P&gt;
&lt;P&gt;Microsoft 365 Copilot is licensed per user, providing a predictable cost structure for ongoing everyday productivity assistance.&lt;/P&gt;
&lt;P&gt;Copilot Cowork operates on a usage-based model using Copilot credits. These credits are pooled at the tenant level and consumed based on task complexity, frequency, and execution requirements. Organizations can manage usage through budgets, alerts, and governance controls.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Choosing the Right Tool&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;A simple decision approach helps determine which tool to use:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;If the task involves creating, summarizing, analyzing, or understanding information within normal work activities, Microsoft 365 Copilot is the appropriate choice.&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI&gt;If the task requires multi-step execution, automation, scheduling, or event-driven workflows, Copilot Cowork is more suitable.&lt;/LI&gt;
&lt;/UL&gt;
&lt;UL&gt;
&lt;LI&gt;If Microsoft 365 Copilot can complete the task effectively under user direction, it should remain the default option.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Cowork should be reserved for higher-value, process-oriented automation where autonomous execution delivers clear business value.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Governance and Responsible Use&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Because Copilot Cowork consumes metered credits, organizations are encouraged to implement governance controls before scaling usage. This includes:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Spending policies and budgets&lt;/LI&gt;
&lt;LI&gt;Usage alerts and monitoring&lt;/LI&gt;
&lt;LI&gt;Credit limits and cost management strategies&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This ensures that automation is aligned with business value and resource consumption is properly managed.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Summary&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Microsoft 365 Copilot enhances everyday productivity by assisting users within their workflow, while Copilot Cowork extends AI into autonomous execution of structured business processes. Together, they provide a layered approach to AI in the workplace—balancing human-guided assistance with scalable automation.&lt;/P&gt;
&lt;P&gt;Choosing the right tool depends on the nature of the work: interactive support versus end-to-end execution. When used appropriately, both can significantly improve efficiency and operational effectiveness across modern organizations.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Sep 2026 16:57:13 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/copilot-or-copilot-cowork-which-tool-to-use-and-when/ba-p/4555402</guid>
      <dc:creator>NicholasAquino</dc:creator>
      <dc:date>2026-09-10T16:57:13Z</dc:date>
    </item>
    <item>
      <title>AI where and when you need it with Dragon Copilot's ability to focus</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/ai-where-and-when-you-need-it-with-dragon-copilot-s-ability-to/ba-p/4554293</link>
      <description>&lt;P&gt;At HIMSS 2026, we showed that the most useful place to apply clinical intelligence is often not in a separate app or side window, but at the cursor, in the field where the clinician is already working. Our &lt;A href="https://techcommunity.microsoft.com/blog/HealthcareAndLifeSciencesBlog/from-dictation-to-intelligence-at-the-cursor-with-dragon-copilot-desktop/4496145" target="_blank" rel="noopener"&gt;last post&lt;/A&gt; on this topic described the problem Dragon Copilot's focus capability is designed to solve: clinicians becoming data couriers, moving between windows, copying information from one system into another, and stitching together a day's work across multiple applications. That post looked ahead to what was coming. Now, it's here.&lt;/P&gt;
&lt;H3&gt;What Dragon Copilot's focus capability does&lt;/H3&gt;
&lt;P&gt;Dragon Copilot's focus capability brings AI directly into the text field where clinicians work, whether that's an EHR, a browser, Microsoft Word, SharePoint, or another desktop application. There is no separate application to launch and no workflow to rebuild.&lt;/P&gt;
&lt;P&gt;Simply place your cursor where you're working, select content if needed, and ask for help using natural language by voice or text. The focus capability works directly within the application you're already using, helping you stay in the flow of work.&lt;/P&gt;
&lt;P&gt;With focus, Dragon Copilot can:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Read content from applications such as an EHR, browser, Microsoft Word, SharePoint, and other desktop applications.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Answer questions about selected content and provide responses in context, using information from trusted sources and resources approved by the organization.&lt;/LI&gt;
&lt;LI&gt;Surface relevant information and insights without requiring manual searches, copying, or pasting.&lt;/LI&gt;
&lt;LI&gt;Generate, edit, and refine text directly where you're working.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The experience is conversational and voice-first. Because the focus capability operates directly at the cursor, clinicians can take action without switching applications or rebuilding context.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;img /&gt;
&lt;P class="lia-align-center"&gt;&lt;EM&gt;Questions are answered in context using information from the EHR and trusted sources, including resources approved by the organization.&lt;/EM&gt;&lt;/P&gt;
&lt;H3&gt;Focus in action&lt;/H3&gt;
&lt;P&gt;The following examples illustrate how Dragon Copilot's focus capability helps clinicians read, answer, write, edit and surface information directly within their workflow.&lt;/P&gt;
&lt;H4&gt;Journal and guideline Q&amp;amp;A&lt;/H4&gt;
&lt;P&gt;Highlight a passage from a clinical guideline or journal article and ask:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"Summarize the three key takeaways in patient-friendly language for the after-visit summary."&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;The focus capability analyzes the selected content and generates a draft directly where you're working.&lt;/P&gt;
&lt;H4&gt;Answer questions in context&lt;/H4&gt;
&lt;P&gt;Clinicians often have the information they need in front of them but spend valuable time locating or interpreting it.&lt;/P&gt;
&lt;P&gt;Highlight relevant content and ask:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"What does this recommendation mean for a patient with diabetes?"&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;The focus capability reviews the selected information and delivers an answer within the workflow, without requiring clinicians to leave the application. The information is sourced from the EHR, a credible source such as MSD Manual, DailyMed, Medline Plus or from an organization’s internal source.&lt;/P&gt;
&lt;H4&gt;Edit in place&lt;/H4&gt;
&lt;P&gt;Select existing text and ask:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"Convert this into a bulleted list." &lt;/EM&gt;or &lt;EM&gt;"Summarize this HPI in two sentences."&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;The focus capability reshapes the content directly where it already exists, helping clinicians refine documentation without disrupting their workflow.&lt;/P&gt;
&lt;H4&gt;Surface relevant information&lt;/H4&gt;
&lt;P&gt;Place your cursor inside a note and ask:&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"What's the patient's BMI?"&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;The focus capability can retrieve relevant information available in context and return the answer inline, eliminating the need to navigate between screens, search for values, or perform calculations manually.&lt;/P&gt;
&lt;H4&gt;Generate new content&lt;/H4&gt;
&lt;P&gt;Need a referral letter, patient instruction, or summary?&lt;/P&gt;
&lt;P&gt;Simply ask.&lt;/P&gt;
&lt;P&gt;The focus capability can generate content directly within the destination field, helping clinicians create documentation where it belongs without copying and pasting between applications.&lt;/P&gt;
&lt;H3&gt;Why this capability matters&lt;/H3&gt;
&lt;P&gt;Bringing AI directly to the cursor is more than a convenience. It's what makes AI practical, visible, and actionable within everyday clinical workflows.&lt;/P&gt;
&lt;P&gt;Dragon Copilot's focus capability sits in a useful middle ground between ambient AI, which operates largely in the background, and traditional dictation, which requires clinicians to explicitly construct documentation themselves.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Outputs are reviewable and editable before being finalized.&lt;/LI&gt;
&lt;LI&gt;Actions remain visible within the workflow, providing transparency and control.&lt;/LI&gt;
&lt;LI&gt;Clinicians can work without repeatedly navigating between applications or rebuilding context.&lt;/LI&gt;
&lt;LI&gt;Because the focus capability operates directly at the cursor, it creates an extensible foundation for future Dragon Copilot experiences and integrations from Microsoft and partners.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;When Dragon Copilot's focus capability brings AI directly to where clinicians are already working, copying, pasting, and window-switching fall away. Clinicians can access information, generate content, and take action without leaving their workflow, helping them spend less time managing technology and more time focused on patient care.&lt;/P&gt;
&lt;P&gt;Learn more about &lt;A href="https://www.microsoft.com/en-us/health-solutions/clinical-workflow/dragon-copilot" target="_blank" rel="noopener"&gt;Dragon Copilot&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2026 16:12:22 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/ai-where-and-when-you-need-it-with-dragon-copilot-s-ability-to/ba-p/4554293</guid>
      <dc:creator>sarahgrey</dc:creator>
      <dc:date>2026-09-09T16:12:22Z</dc:date>
    </item>
    <item>
      <title>Notes and documents – the way clinicians want them</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/notes-and-documents-the-way-clinicians-want-them/ba-p/4554064</link>
      <description>&lt;H4&gt;&lt;STRONG&gt;The moment after the visit&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;There is a moment in every patient encounter when the clinical story needs to become something more than a note. It may become a referral letter, a set of patient instructions, a school or work note, or a summary that helps a patient remember what was discussed.&lt;/P&gt;
&lt;P&gt;These documents matter as much as the note itself. A patient needs clear instructions they can understand and follow. A referring physician needs concise context and clinical reasoning. A specialist needs relevant background. Each audience is different; each document has a different purpose. For clinicians, these documents are not administrative leftovers. They are part of care itself. They carry the reasoning, reassurance, precision, and next steps that help patients and care teams move forward with confidence. And yet, creating them often happens under pressure and requires clinicians to rely on memory, whether they are documenting in between patients or after clinic hours.&lt;/P&gt;
&lt;H4&gt;&lt;STRONG&gt;Introducing custom document templates in Dragon Copilot&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;Dragon Copilot's custom document templates are designed to solve this problem by allowing the clinician to create these documents directly in the workflow. A custom document template is a reusable, AI-generated structure that turns a clinical encounter into the right finished document — a referral letter, after-visit summary, work note, pre-operative instructions — in the format the clinician defines.&lt;/P&gt;
&lt;H4&gt;&lt;STRONG&gt;How it works&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;A clinician describes what they need in plain language:&amp;nbsp;&lt;EM&gt;"Create a patient-friendly follow-up letter after a cardiology visit."&lt;/EM&gt; Dragon Copilot generates a draft template from that description. The clinician can then refine it — by speaking naturally— to adjust the tone, the structure, or the level of clinical detail until it reflects how they communicate. The finished template is saved and reusable, and ready to populate from the next encounter's notes.&lt;/P&gt;
&lt;P&gt;Templates can be built from scratch with a prompt, from a pasted sample, or from an uploaded file, with a preview before the template is used with real patient data.&lt;/P&gt;
&lt;img /&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;STRONG&gt;Built around how each clinician works&amp;nbsp;&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;Imagine a clinician finishing a consultation. The conversation was nuanced. The patient asked thoughtful questions. The next step requires a referral letter that reflects not only the diagnosis, but also the clinical reasoning behind it.&lt;/P&gt;
&lt;P&gt;Traditionally, that letter may be written later, when the clinician is already thinking about the next patient, the next inbox message, or the next task. With custom documents, the clinician can define the structure they need, save it, and generate the right type of output directly in the workflow.&lt;/P&gt;
&lt;P&gt;Referral letters are just one example. Clinicians create a wide range of documents every day, each designed for a different audience and purpose.&lt;/P&gt;
&lt;P&gt;A pediatrician needs parent-friendly discharge instructions — plain language, no jargon, clear next steps. A surgeon needs structured pre-operative guidance that follows a consistent format every time. A general practitioner needs a concise work note that takes seconds, not minutes. A specialist needs a referral response that reflects both the diagnosis and the clinical reasoning behind it.&lt;/P&gt;
&lt;P&gt;Each of these is a different template, built once, refined in conversation, and reused whenever it is needed. The AI adapts to the clinician's specialty, communication style, and intended audience — not the other way around.&lt;/P&gt;
&lt;H4&gt;&lt;STRONG&gt;Clinical impact in real-world workflows&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;Custom documents can create value where clinicians feel pressure most: in the moments after the encounter, when the clinical conversation needs to become clear, actionable communication. In practice, this means less time spent on repetitive drafting, manual rework, switching between documentation tasks, reconstructing details after the visit, creating routine letters, instructions, or summaries from scratch.&lt;/P&gt;
&lt;P&gt;Custom documents help make documentation more flexible, reusable, and aligned with how care is delivered.&lt;/P&gt;
&lt;H4&gt;&lt;STRONG&gt;A step toward a more human future&lt;/STRONG&gt;&lt;/H4&gt;
&lt;P&gt;Less time spent drafting, reworking, and reconstructing details after the visit. More consistency across documents. And clinical communication that reflects how care was delivered — not a generic approximation of it. Custom documents help turn the conversation in the exam room into the right document for the right moment, with less friction and more consistency&lt;/P&gt;
&lt;P&gt;The goal is a future where clinicians do not have to choose between being present in the room and being precise in the record. Custom document templates in Dragon Copilot are a step toward that future.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-------------&lt;/P&gt;
&lt;P&gt;Click here to learn more about &lt;A href="https://www.microsoft.com/en-us/health-solutions/clinical-workflow/dragon-copilot" target="_blank" rel="noopener"&gt;Dragon Copilot&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2026 15:29:10 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/notes-and-documents-the-way-clinicians-want-them/ba-p/4554064</guid>
      <dc:creator>rhitac</dc:creator>
      <dc:date>2026-09-08T15:29:10Z</dc:date>
    </item>
    <item>
      <title>Using Copilot in Sensitive Healthcare Teams Meetings - Without Recording or Transcription</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/using-copilot-in-sensitive-healthcare-teams-meetings-without/ba-p/4553097</link>
      <description>&lt;P&gt;Healthcare organizations want the productivity benefits of Microsoft 365 Copilot, but those benefits must be balanced with privacy, security, and compliance requirements.&lt;/P&gt;
&lt;P&gt;I recently worked with a healthcare customer whose compliance team was concerned about persistent meeting artifacts. They wanted users to benefit from Copilot during Microsoft Teams meetings, but they did not want every conversation recorded or a transcript available afterward—especially for meetings involving sensitive operational, workforce, legal, compliance, or patient-related discussions.&lt;/P&gt;
&lt;P&gt;Microsoft Teams provides an option that can help with this scenario: allowing Copilot &lt;STRONG&gt;only during the meeting&lt;/STRONG&gt; while disabling recording and transcription.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Important:&lt;/STRONG&gt; This article describes a technical configuration and customer scenario. It is not legal or compliance advice. Your privacy, security, compliance, records-management, and legal teams should determine whether this configuration is appropriate for your organization and specific meeting types.&lt;/P&gt;
&lt;H2&gt;Why This Matters in Healthcare&lt;/H2&gt;
&lt;P&gt;Healthcare organizations conduct many meetings where the discussion may include sensitive information:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Patient care coordination&lt;/LI&gt;
&lt;LI&gt;Quality and safety reviews&lt;/LI&gt;
&lt;LI&gt;Compliance investigations&lt;/LI&gt;
&lt;LI&gt;Workforce and employee matters&lt;/LI&gt;
&lt;LI&gt;Security incidents&lt;/LI&gt;
&lt;LI&gt;Legal or risk-management discussions&lt;/LI&gt;
&lt;LI&gt;Research and clinical program planning&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;A recording or transcript can become an additional persistent information asset that must be appropriately protected, retained, governed, and eventually disposed of.&lt;/P&gt;
&lt;P&gt;The HIPAA Security Rule requires covered entities and business associates to implement reasonable and appropriate administrative, physical, and technical safeguards for electronic protected health information. This includes evaluating risk, controlling access, implementing audit controls, and periodically reviewing security measures. &lt;A href="https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html" target="_blank"&gt;The U.S. Department of Health and Human Services provides an overview of these requirements here.&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;HIPAA’s minimum necessary standard also generally calls for organizations to limit unnecessary access to protected health information, although important exceptions apply—including certain disclosures for treatment. &lt;A href="https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/minimum-necessary-requirement/index.html" target="_blank"&gt;HHS provides additional guidance on the minimum necessary requirement.&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Turning off recording and transcription does not automatically make a meeting compliant. However, reducing the creation of unnecessary meeting artifacts can be one useful part of a broader, risk-based healthcare data-governance strategy.&lt;/P&gt;
&lt;H2&gt;Copilot Without a Persistent Transcript&lt;/H2&gt;
&lt;P&gt;When a Teams meeting is configured for &lt;STRONG&gt;Only during the meeting&lt;/STRONG&gt;, Copilot can use temporary speech-to-text data to understand the active conversation. A traditional meeting transcript does not need to be started.&lt;/P&gt;
&lt;P&gt;Users can ask Copilot to:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Summarize what has been discussed&lt;/LI&gt;
&lt;LI&gt;Identify decisions&lt;/LI&gt;
&lt;LI&gt;List open questions&lt;/LI&gt;
&lt;LI&gt;Capture action items&lt;/LI&gt;
&lt;LI&gt;Explain areas of disagreement&lt;/LI&gt;
&lt;LI&gt;Help someone catch up after joining late&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Microsoft explains that Copilot must be manually started by a participant in this configuration. Copilot can then provide insights based on the conversation taking place while it is active. &lt;A href="https://support.microsoft.com/en-us/teams/copilot/use-copilot-without-transcribing-or-recording-a-teams-meeting-or-call" target="_blank"&gt;See Microsoft’s guidance for using Copilot without recording or transcribing a Teams meeting.&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;There are two important limitations users must understand.&lt;/P&gt;
&lt;P&gt;First, Copilot does not automatically start when the meeting begins. If someone activates it five minutes into the meeting, it will not have the same context it would have had if it had been started at the beginning.&lt;/P&gt;
&lt;P&gt;Second, users should capture anything they need before leaving the meeting. Without transcription, they will not have the same post-meeting Copilot conversation history or transcript-based recap. Microsoft recommends copying any Copilot content users want to keep before the meeting ends.&lt;/P&gt;
&lt;H2&gt;Watch the Complete Walkthrough&lt;/H2&gt;
&lt;P&gt;In the following video, I demonstrate the user experience, the corresponding Teams administrative policies, the Facilitator consideration, and several lessons I learned while implementing this for a healthcare customer.&lt;/P&gt;
&lt;div data-video-id="https://youtu.be/xrDHQ-_NOwA?si=CON4CU_lnpLblB24/1788451327453" data-video-remote-vid="https://youtu.be/xrDHQ-_NOwA?si=CON4CU_lnpLblB24/1788451327453" class="lia-video-container lia-media-is-center lia-media-size-large"&gt;&lt;iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FxrDHQ-_NOwA%3Ffeature%3Doembed&amp;amp;display_name=YouTube&amp;amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxrDHQ-_NOwA&amp;amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FxrDHQ-_NOwA%2Fhqdefault.jpg&amp;amp;type=text%2Fhtml&amp;amp;schema=youtube" allowfullscreen="" style="max-width: 100%"&gt;&lt;/iframe&gt;&lt;/div&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;How to Use Copilot in Teams Without Recording or Transcription: Admin Setup &amp;amp; Gotchas&lt;/EM&gt;&lt;/P&gt;
&lt;H2&gt;The Administrative Configuration&lt;/H2&gt;
&lt;P&gt;For this scenario, the goal was to create a scoped Teams meeting policy that:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Prevented users from recording meetings&lt;/LI&gt;
&lt;LI&gt;Prevented users from starting transcription&lt;/LI&gt;
&lt;LI&gt;Allowed Copilot to operate during the meeting&lt;/LI&gt;
&lt;LI&gt;Avoided enabling a transcript-dependent post-meeting Copilot experience&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The settings are managed through Teams meeting policies in the Teams admin center. In the video, I walk through the relevant recording, transcription, and Copilot controls and show the resulting experience from a user’s perspective.&lt;/P&gt;
&lt;P&gt;For a healthcare organization, I would normally begin with a limited population instead of immediately applying a new policy globally. A pilot group gives the organization an opportunity to test the technical behavior and evaluate it with stakeholders from:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Privacy and compliance&lt;/LI&gt;
&lt;LI&gt;Information security&lt;/LI&gt;
&lt;LI&gt;Legal and risk management&lt;/LI&gt;
&lt;LI&gt;Records management&lt;/LI&gt;
&lt;LI&gt;Clinical or operational leadership&lt;/LI&gt;
&lt;LI&gt;Microsoft 365 administration&lt;/LI&gt;
&lt;LI&gt;End-user training and adoption&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The appropriate configuration may differ between clinical, administrative, research, legal, HR, and general collaboration scenarios. A single organization-wide meeting policy may not be the right answer for every healthcare meeting.&lt;/P&gt;
&lt;H2&gt;“No Transcript” Does Not Mean “No Compliance Data”&lt;/H2&gt;
&lt;P&gt;This distinction is critical.&lt;/P&gt;
&lt;P&gt;Although participants may not receive a traditional meeting recording or transcript, Copilot prompts and responses can still be subject to Microsoft Purview retention policies. Depending on the organization’s configuration, those interactions may also be discoverable through Microsoft Purview eDiscovery.&lt;/P&gt;
&lt;P&gt;Microsoft explicitly notes that Copilot prompts and responses may be retained for compliance purposes even when recording and transcription are disabled. &lt;A href="https://learn.microsoft.com/en-us/training/modules/purview-ai-data-compliance/" target="_blank"&gt;Microsoft’s Purview training covers auditing, retention, eDiscovery, and compliance controls for Copilot interactions.&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Healthcare organizations should therefore evaluate more than the visible Teams recap. The governance review should include:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Copilot interaction retention&lt;/LI&gt;
&lt;LI&gt;Microsoft Purview Audit&lt;/LI&gt;
&lt;LI&gt;eDiscovery requirements&lt;/LI&gt;
&lt;LI&gt;Data Loss Prevention policies&lt;/LI&gt;
&lt;LI&gt;Sensitivity labels&lt;/LI&gt;
&lt;LI&gt;Records-management obligations&lt;/LI&gt;
&lt;LI&gt;Access to saved notes or exported Copilot responses&lt;/LI&gt;
&lt;LI&gt;Organizational policies governing the entry of PHI into AI-assisted experiences&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The user experience may feel temporary, but the organization’s compliance controls can still operate behind the scenes.&lt;/P&gt;
&lt;H2&gt;The Lesson We Almost Missed: Facilitator Still Creates Loop Artifacts&lt;/H2&gt;
&lt;P&gt;This was one of the most important lessons from my recent engagement.&lt;/P&gt;
&lt;P&gt;While working to Copilot to operate only during the meeting. Recording was disabled, transcription was disabled, and users did not receive the traditional transcript-based recap we were trying to avoid.&lt;/P&gt;
&lt;P&gt;But Loop files were still appearing.&lt;/P&gt;
&lt;P&gt;That initially seemed inconsistent with the policy design. After investigating, we discovered that the files were not being created by the personal Copilot experience—they were being generated because &lt;STRONG&gt;Microsoft Facilitator was enabled&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;This distinction is easy to miss:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Copilot only during the meeting&lt;/STRONG&gt; gives an individual user private, real-time assistance without requiring a persistent transcript.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Facilitator&lt;/STRONG&gt; is a shared meeting agent that can generate collaborative notes and other meeting artifacts.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Microsoft documents that Facilitator’s meeting data is stored as a .loop file in the &lt;STRONG&gt;Meetings&lt;/STRONG&gt; folder of the OneDrive account belonging to the user who initiated Facilitator. The data is treated as meeting transcript data for governance purposes. Facilitator notes may also be available to meeting participants through Notes and the meeting recap. &lt;A href="https://learn.microsoft.com/en-us/microsoftteams/facilitator-teams" target="_blank"&gt;Microsoft documents Facilitator’s behavior, storage, and administrative controls here.&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;For a healthcare organization, that Loop file is not simply a convenient set of notes. Depending on what was discussed, it could contain sensitive operational information, workforce information, security details, or protected health information. It becomes another persistent artifact that must be considered in the organization’s access, sharing, retention, eDiscovery, lifecycle-management, and data-protection strategy.&lt;/P&gt;
&lt;H3&gt;Copilot and Facilitator Require Separate Governance Decisions&lt;/H3&gt;
&lt;P&gt;Disabling recording and transcription while allowing Copilot during the meeting does not automatically prevent Facilitator from producing shared meeting content.&lt;/P&gt;
&lt;P&gt;Healthcare organizations should make separate decisions about:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Whether users should have access to Copilot during meetings.&lt;/LI&gt;
&lt;LI&gt;Whether users should be allowed to initiate Facilitator.&lt;/LI&gt;
&lt;LI&gt;Which meeting types are appropriate for shared AI-generated notes.&lt;/LI&gt;
&lt;LI&gt;Which users or groups should be allowed to use Facilitator.&lt;/LI&gt;
&lt;LI&gt;How the resulting Loop files should be stored, accessed, retained, labeled, and disposed of.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Facilitator can be extremely useful for approved operational meetings where collaborative notes, decisions, and follow-up actions are valuable. However, it may not be appropriate for every sensitive clinical, compliance, legal, HR, or incident-response meeting.&lt;/P&gt;
&lt;P&gt;Microsoft allows administrators to control whether Facilitator is available across the organization or only to selected groups of users through Teams app policies and app-centric management. One important administrative nuance is that access to Facilitator can be scoped, while Microsoft’s control for turning off AI-generated meeting notes is currently tenant-wide rather than user-specific.&lt;/P&gt;
&lt;P&gt;That makes intentional scoping particularly important. Instead of assuming every Copilot-licensed user should also be able to initiate Facilitator, organizations can identify the populations and meeting scenarios where persistent collaborative notes have a defined business purpose and an approved governance model.&lt;/P&gt;
&lt;P&gt;The practical lesson is simple:&lt;/P&gt;
&lt;P&gt;If your goal is to use Copilot without creating persistent meeting artifacts, do not stop after validating the recording, transcription, and Copilot policies. Verify whether Facilitator is enabled and inspect the resulting Loop behavior as part of your testing.&lt;/P&gt;
&lt;H2&gt;The Meeting Option That Can Cause Confusion and Broke Things For Us&lt;/H2&gt;
&lt;P&gt;One of the most important lessons from this implementation involved the meeting organizer’s Copilot setting.&lt;/P&gt;
&lt;P&gt;If an organizer changes the meeting from &lt;STRONG&gt;Only during the meeting&lt;/STRONG&gt; to &lt;STRONG&gt;During and after the meeting&lt;/STRONG&gt;, Copilot expects transcription to be available. If the organization’s policy prevents transcription, the user may receive an error indicating that Copilot cannot access the meeting.&lt;/P&gt;
&lt;P&gt;From the user’s perspective, that can look like a licensing problem or a broken Copilot deployment. In reality, it may simply be a mismatch between:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The organization’s transcription policy&lt;/LI&gt;
&lt;LI&gt;The Copilot meeting option selected by the organizer&lt;/LI&gt;
&lt;LI&gt;The type of Copilot experience the user is attempting to start&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Microsoft’s meeting guidance confirms that &lt;STRONG&gt;During and after the meeting&lt;/STRONG&gt; requires transcription, while &lt;STRONG&gt;Only during the meeting&lt;/STRONG&gt; can operate without it. &lt;A href="https://support.microsoft.com/en-us/copilot-teams" target="_blank"&gt;Review the current Copilot behavior in Microsoft Teams meetings.&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;This is why user education is just as important as the policy itself.&lt;/P&gt;
&lt;H2&gt;A Healthcare Deployment Checklist&lt;/H2&gt;
&lt;P&gt;Before introducing this configuration more broadly, consider the following:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;&lt;STRONG&gt;Classify the meeting scenarios.&lt;/STRONG&gt; Determine where in-meeting Copilot is appropriate and where AI assistance should be restricted entirely.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Engage compliance early.&lt;/STRONG&gt; Validate the design with privacy, security, legal, records-management, and compliance stakeholders.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Use scoped policies.&lt;/STRONG&gt; Pilot with specific users or groups before considering a broader rollout.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Review more than recordings and transcripts.&lt;/STRONG&gt; Evaluate Purview retention, auditing, eDiscovery, DLP, sensitivity labels, and exported Copilot content.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Evaluate and scope Facilitator separately.&lt;/STRONG&gt; Determine which users should be able to initiate Facilitator and which meeting scenarios justify shared AI-generated notes. Test where the resulting Loop files are stored, who can access them, and how retention, sensitivity labels, eDiscovery, sharing, and lifecycle controls apply.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Test for unexpected artifacts.&lt;/STRONG&gt; After a pilot meeting, inspect the organizer’s and initiator’s OneDrive, the meeting chat, Notes, Recap, Loop, and relevant Purview experiences. Confirm that the meeting produces only the artifacts your governance team expects.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Train meeting organizers.&lt;/STRONG&gt; Explain the difference between &lt;STRONG&gt;Only during the meeting&lt;/STRONG&gt; and &lt;STRONG&gt;During and after the meeting&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Prepare users for the temporary experience.&lt;/STRONG&gt; Users should capture approved action items or summaries before the meeting ends.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Test the complete workflow.&lt;/STRONG&gt; Validate the experience using representative accounts, policies, licenses, meeting types, and organizational controls.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Review the configuration periodically.&lt;/STRONG&gt; Microsoft Teams and Copilot capabilities continue to evolve, and healthcare organizations should reassess their controls as features change.&lt;/LI&gt;
&lt;/OL&gt;
&lt;H2&gt;Finding the Right Balance&lt;/H2&gt;
&lt;P&gt;Healthcare organizations do not necessarily have to choose between disabling Copilot completely and generating a recording and transcript for every meeting.&lt;/P&gt;
&lt;P&gt;The &lt;STRONG&gt;Only during the meeting&lt;/STRONG&gt; option provides another path: users can receive real-time assistance while the organization limits the creation of traditional post-meeting artifacts.&lt;/P&gt;
&lt;P&gt;It is not a substitute for a complete healthcare compliance strategy. It is a technical control that can support a broader strategy built around risk assessment, appropriate access, retention, auditing, training, and clearly defined meeting scenarios.&lt;/P&gt;
&lt;P&gt;The Facilitator lesson also demonstrates why organizations must test the entire meeting experience—not just the most visible policy settings. Copilot may be operating as expected while another enabled capability is still creating shared, persistent content.&lt;/P&gt;
&lt;P&gt;For the healthcare customer that inspired this video, the technical settings were only part of the solution. The real success came from understanding the user experience, finding the unexpected Loop artifacts, separating Copilot governance from Facilitator governance, and teaching organizers how the different options behave.&lt;/P&gt;
&lt;P&gt;That is the lesson I hope this walkthrough helps other healthcare organizations apply.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2026 16:02:15 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/using-copilot-in-sensitive-healthcare-teams-meetings-without/ba-p/4553097</guid>
      <dc:creator>michaelgoad</dc:creator>
      <dc:date>2026-09-03T16:02:15Z</dc:date>
    </item>
    <item>
      <title>Extend clinical workflows with Dragon Copilot AI Apps and Agents in Microsoft Marketplace</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/extend-clinical-workflows-with-dragon-copilot-ai-apps-and-agents/ba-p/4548688</link>
      <description>&lt;P&gt;&lt;STRONG&gt;GA ANNOUNCEMENT&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Today, we're excited to announce the General Availability (GA) of &lt;A class="lia-external-url" href="https://marketplace.microsoft.com/en-us/search/products?page=1&amp;amp;product=dragon-copilot%3Bcopilot" target="_blank" rel="noopener"&gt;Dragon Copilot AI Apps and Agents&lt;/A&gt; for physician workflows, a major milestone in building an open and trusted healthcare AI ecosystem.&lt;/P&gt;
&lt;P&gt;Healthcare organizations can now discover, build, deploy, and manage trusted AI-powered applications and agents that support specialized clinical and operational capabilities through &lt;A class="lia-external-url" href="https://www.microsoft.com/en-us/health-solutions/clinical-workflow/dragon-copilot?msockid=1e028d01d8946f5012f39832d93f6e9b" target="_blank" rel="noopener"&gt;Dragon Copilot&lt;/A&gt;. At the same time, partners can use self-service experiences to build, validate, certify, publish, and manage solutions that integrate directly into clinician workflows.&lt;/P&gt;
&lt;P&gt;Together, these capabilities bring healthcare organizations, clinicians, and partners onto a common platform designed to accelerate innovation while maintaining the trust, transparency, and governance required in healthcare.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;div data-video-id="https://www.youtube.com/watch?v=vkLcB-2DH74/1787257004417" data-video-remote-vid="https://www.youtube.com/watch?v=vkLcB-2DH74/1787257004417" class="lia-video-container lia-media-is-center lia-media-size-large"&gt;&lt;iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FvkLcB-2DH74%3Ffeature%3Doembed&amp;amp;display_name=YouTube&amp;amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DvkLcB-2DH74&amp;amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FvkLcB-2DH74%2Fhqdefault.jpg&amp;amp;type=text%2Fhtml&amp;amp;schema=youtube" allowfullscreen="" style="max-width: 100%"&gt;&lt;/iframe&gt;&lt;/div&gt;
&lt;H1&gt;Why it matters to clinicians&lt;/H1&gt;
&lt;P&gt;Clinicians need relevant insights delivered in the flow of care—not in another disconnected tool. Dragon Copilot AI Apps and Agents can surface specialized intelligence within existing workflows to support coding and documentation, medical decision-making, risk adjustment, prior authorization, diagnostic support, behavioral health screening, and preventive care. Dragon Copilot AI Apps and Agents for physicians provide capabilities for use cases such as:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Coding and documentation optimization (&lt;A class="lia-external-url" href="https://marketplace.microsoft.com/en-us/product/regard.regard-extension?tab=Overview" target="_blank" rel="noopener"&gt;Regard&lt;/A&gt;, &lt;A class="lia-external-url" href="https://marketplace.microsoft.com/en-us/product/rhythmxaillc1780436102845.gw-rhythmx-precision-care?tab=Overview" target="_blank" rel="noopener"&gt;RhythmX AI&lt;/A&gt;)&lt;/LI&gt;
&lt;LI&gt;Risk adjustment (&lt;A class="lia-external-url" href="https://marketplace.microsoft.com/en-us/product/raapidinc1737396201493.raapid_ambient_hcc_capture?tab=Overview" target="_blank" rel="noopener"&gt;RAAPID Inc&lt;/A&gt;)&lt;/LI&gt;
&lt;LI&gt;Prior authorization (&lt;A class="lia-external-url" href="https://marketplace.microsoft.com/en-us/product/humatahealth.humatahealth_dragonpaautomation?tab=Overview" target="_blank" rel="noopener"&gt;Humata Health&lt;/A&gt;, &lt;A class="lia-external-url" href="https://marketplace.microsoft.com/en-us/product/genzeon.hiponepriorauthintelligence?tab=Overview" target="_blank" rel="noopener"&gt;Genzeon&lt;/A&gt;)&lt;/LI&gt;
&lt;LI&gt;Evidence-Based Hyper-Personalized Care Guidance (&lt;A class="lia-external-url" href="https://marketplace.microsoft.com/en-us/product/atroposhealthinc1782313269471.atropos-evidence-agent-dragon?tab=Overview" target="_blank" rel="noopener"&gt;Atropos Health&lt;/A&gt;)&lt;/LI&gt;
&lt;LI&gt;Diagnostic support (Coming soon!)&lt;/LI&gt;
&lt;LI&gt;Cognitive &amp;amp; behavioral health screening (&lt;A class="lia-external-url" href="https://marketplace.microsoft.com/en-us/product/canaryspeechinc1680821199981.canary-ambient-for-physicians?tab=Overview" target="_blank" rel="noopener"&gt;Canary Speech&lt;/A&gt;)&lt;/LI&gt;
&lt;LI&gt;Care Gaps &amp;amp; Preventive Health Reminders (Coming soon!)&lt;/LI&gt;
&lt;LI&gt;Clinician coaching (&lt;A class="lia-external-url" href="https://marketplace.microsoft.com/en-us/product/whetstonehealth.whetstone-communication-intelligence?tab=Overview" target="_blank" rel="noopener"&gt;Whetstone Health&lt;/A&gt;)&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;By bringing the right information into the physician’s existing workflow and using patient data from the EHR and the Dragon ambient context (audio, transcript and clinical note) to make insights more relevant, these capabilities can reduce context switching, streamline administrative work, and help physicians stay focused on patient care while maintaining clinical judgment and control workflows.&lt;/P&gt;
&lt;H1&gt;Why it matters to healthcare organizations&lt;/H1&gt;
&lt;P&gt;Healthcare organizations need a scalable way to expand the value of Dragon Copilot while maintaining enterprise governance. AI Apps and Agents provide access to a growing portfolio of specialized capabilities through a common platform, helping organizations increase return on their Dragon Copilot investment without adding fragmented solutions.&amp;nbsp;&lt;A class="lia-external-url" href="https://learn.microsoft.com/en-us/industry/healthcare/dragon-copilot/whats-new/5-0#dragon-copilot-ai-apps-and-agents" target="_blank" rel="noopener"&gt;Dragon Copilot AI Apps and Agents&lt;/A&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Helps increase ROI by extending Dragon Copilot across more clinical and operational use cases, seamlessly integrated into workflow&lt;/LI&gt;
&lt;LI&gt;Simplify solution discovery and purchase through Microsoft Marketplace&lt;/LI&gt;
&lt;LI&gt;Centralize deployment, policy, and lifecycle governance through the &lt;A class="lia-external-url" href="https://learn.microsoft.com/en-us/industry/healthcare/dragon-admin-center/" target="_blank" rel="noopener"&gt;Dragon Admin Center&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;Maintain clinician oversight and organizational standards for security, privacy, compliance, and responsible AI&lt;/LI&gt;
&lt;LI&gt;Reduce implementation burden with streamlined experiences that require minimal IT lift&lt;/LI&gt;
&lt;LI&gt;Build and deploy custom built apps/agents integrated with Dragon Copilot&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;This creates a governed, scalable path to adopt new capabilities faster, making it easier to evaluate solutions, deploy them across teams, manage them consistently, and measure value without unnecessary operational complexity.&lt;/P&gt;
&lt;H1&gt;Why it matters to partners&lt;/H1&gt;
&lt;P&gt;Healthcare AI companies often have valuable, specialized capabilities but face significant complexity bringing them into clinical workflows and deploying them consistently across healthcare organizations. Dragon Copilot AI Apps and Agents give partners a standardized extensibility model for embedding their innovations where clinicians already work.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Access ambient, patient and encounter context to deliver more relevant, timely experiences&lt;/LI&gt;
&lt;LI&gt;Integrate into the Dragon Copilot experience without building and maintaining bespoke workflow integrations for every customer&lt;/LI&gt;
&lt;LI&gt;Use self-service onboarding,&lt;A class="lia-external-url" href="https://review.learn.microsoft.com/en-us/legal/marketplace/certification-policies?branch=main&amp;amp;branchFallbackFrom=pr-en-us-2269#60001-value-proposition-and-offer-requirements" target="_blank" rel="noopener"&gt; technical validation, and applicable compliance certification&lt;/A&gt; to accelerate readiness&lt;/LI&gt;
&lt;LI&gt;Reach healthcare customers through &lt;A class="lia-external-url" href="https://review.learn.microsoft.com/en-us/partner-center/marketplace-offers/plan-dragon-copilot-offer?branch=main&amp;amp;branchFallbackFrom=pr-en-us-12573" target="_blank" rel="noopener"&gt;Microsoft Marketplace&lt;/A&gt; and scale deployment through a trusted enterprise platform&lt;/LI&gt;
&lt;LI&gt;Build customer confidence with transparent solution information and consistent governance expectations&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;By reducing the friction of workflow integration, distribution, and enterprise deployment, the platform helps partners focus on differentiated clinical value while expanding their reach at scale.&lt;/P&gt;
&lt;H1&gt;Creating a trusted healthcare AI ecosystem&lt;/H1&gt;
&lt;P&gt;Dragon Copilot connects specialized partner capabilities with clinical workflows through a trusted &amp;amp; scalable ecosystem. Streamlined self-service onboarding, package validation, compliance certification, and help partner innovations reach the market faster while giving healthcare organizations confidence to adopt and manage these AI solutions responsibly.&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;“Healthcare moves at the speed of trust. You look at Microsoft and Dragon Copilot, we absolutely trust the combination of Microsoft and Dragon Copilot for industry leading innovation, highly trusted, responsible AI, and delivery at scale, and also the reach with the number of clinicians that Dragon Copilot has. And if you combine all these elements of innovation, your reach, track record, and the trust, that's a perfect recipe for partnership.”&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;—&amp;nbsp;&lt;/STRONG&gt;&lt;STRONG&gt;Deepthi Bathina, CEO and Founder, GW RhythmX&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"I use Dragon Copilot in clinic every day. The extension program let me design, build, and implement the tool I wanted to make me a better clinician. It's never been this easy to be both the user and the builder."&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;—&amp;nbsp;&lt;/EM&gt;&lt;STRONG&gt;Aaron Reinke, MD, Family Physician and Founder, Whetstone Health&lt;/STRONG&gt;&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;H2&gt;Explore the ecosystem&lt;/H2&gt;
&lt;H2&gt;For healthcare organizations – discover and deploy&lt;/H2&gt;
&lt;UL&gt;
&lt;LI&gt;Explore how Dragon Copilot AI Apps and Agents on Microsoft &lt;A href="https://marketplace.microsoft.com/en-us/search/products?product=dragon-copilot" target="_blank" rel="noopener"&gt;Marketplace&lt;/A&gt; can deliver specialized AI solutions tailored to your clinical and operational needs through Dragon Copilot.&lt;/LI&gt;
&lt;LI&gt;Discover new capabilities, &lt;A class="lia-external-url" href="https://learn.microsoft.com/en-us/marketplace/purchase-dragon-copilot-app?branch=main&amp;amp;branchFallbackFrom=pr-en-us-12574" target="_blank" rel="noopener"&gt;purchase&lt;/A&gt;and &lt;A class="lia-external-url" href="https://learn.microsoft.com/en-us/industry/healthcare/dragon-admin-center/concepts/ai-apps-agents" target="_blank" rel="noopener"&gt;deploy&lt;/A&gt;trusted solutions, and deliver more value to clinicians without disrupting existing workflows in Dragon Copilot, learn more &lt;A href="https://learn.microsoft.com/en-us/industry/healthcare/dragon-copilot/whats-new/5-0#dragon-copilot-ai-apps-and-agents" target="_blank" rel="noopener"&gt;here&lt;/A&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H2&gt;For partners – build and publish&lt;/H2&gt;
&lt;UL&gt;
&lt;LI&gt;Bring your differentiated expertise directly into Physician workflows by creating and publishing AI Apps and Agents that help healthcare organizations address high-value clinical and operational needs.&amp;nbsp;&lt;A href="https://learn.microsoft.com/en-us/industry/healthcare/dragon-copilot/extensions/" target="_blank" rel="noopener"&gt;Learn how to build and publish applications and agents&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://github.com/microsoft/dragon-copilot-extension-samples/tree/main/physician/src/samples/DragonCopilot/Workflow/SampleExtension.Web" target="_blank" rel="noopener"&gt;Review our open-source code samples&lt;/A&gt; and start building today with Dragon Copilot’s extensibility framework and reach healthcare customers through Microsoft &lt;A href="https://marketplace.microsoft.com/en-us/search/products?product=dragon-copilot" target="_blank" rel="noopener"&gt;Marketplace&lt;/A&gt;.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;&lt;A class="lia-external-url" href="https://review.learn.microsoft.com/en-us/partner-center/marketplace-offers/create-dragon-copilot-offer?branch=main&amp;amp;branchFallbackFrom=pr-en-us-12573" target="_blank" rel="noopener"&gt;Publish&lt;/A&gt;your Dragon offer on Microsoft on Marketplace&lt;/LI&gt;
&lt;/UL&gt;
&lt;H1&gt;Looking ahead&lt;/H1&gt;
&lt;P&gt;&lt;A class="lia-external-url" href="https://learn.microsoft.com/en-us/industry/healthcare/dragon-copilot/" target="_blank" rel="noopener"&gt;Dragon Copilot&lt;/A&gt; is becoming a trusted destination for specialized healthcare AI—bringing partner innovation directly into familiar clinician workflows.&lt;/P&gt;
&lt;P&gt;As the ecosystem grows, we will expand support for Radiology and Nursing Apps and Agents, addressing the distinct role-based needs of multiple clinical personas. We will also evolve the end-user experience to be more adaptable, enabling chat-based experiences, richer interactivity, and new ways for clinicians to engage with partner capabilities in the flow of work. Streamlined self-service, transparent governance, and Marketplace distribution will help partners scale secure solutions while giving healthcare organizations confidence to adopt them.&lt;/P&gt;
&lt;P&gt;Together, we’re helping clinicians spend less time on administration and access the right intelligence at the right moment in care.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Aug 2026 17:04:55 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/extend-clinical-workflows-with-dragon-copilot-ai-apps-and-agents/ba-p/4548688</guid>
      <dc:creator>AlmaChandrasekharan</dc:creator>
      <dc:date>2026-08-21T17:04:55Z</dc:date>
    </item>
    <item>
      <title>How to Set Up Copilot Skills in PowerPoint (and Build Your Own)</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/how-to-set-up-copilot-skills-in-powerpoint-and-build-your-own/ba-p/4548273</link>
      <description>&lt;H1&gt;How to Set Up Copilot Skills in PowerPoint (and Build Your Own)&lt;/H1&gt;
&lt;P&gt;You have a deck you rebuild every month. The business review, the project update, the readout for leadership. Every time, the same work. Cut the bullets down. Fix the capitalization someone else broke. Take 20 slides down to 7 so an executive will read it.&lt;/P&gt;
&lt;P&gt;Copilot in PowerPoint does all of that, and it's good at it. Then next month you open a new deck and type the whole thing out again, because Copilot doesn't remember how you like it done.&lt;/P&gt;
&lt;P&gt;That's the problem skills solve.&lt;/P&gt;
&lt;P&gt;I help organizations roll out Copilot in front of thousands of users, and skills are the feature I see the fewest people using. Plenty of teams are paying for it and have never turned it on.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;div data-video-id="https://youtu.be/0CA-k3FtPX0?si=hUfX9TjBbqfmG3hv/1787190618924" data-video-remote-vid="https://youtu.be/0CA-k3FtPX0?si=hUfX9TjBbqfmG3hv/1787190618924" class="lia-video-container lia-media-is-center lia-media-size-large"&gt;&lt;iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0CA-k3FtPX0%3Ffeature%3Doembed&amp;amp;display_name=YouTube&amp;amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0CA-k3FtPX0&amp;amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F0CA-k3FtPX0%2Fhqdefault.jpg&amp;amp;type=text%2Fhtml&amp;amp;schema=youtube" allowfullscreen="" style="max-width: 100%"&gt;&lt;/iframe&gt;&lt;/div&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H2&gt;What a skill is&lt;/H2&gt;
&lt;P&gt;A skill is a pattern you wrote down once.&lt;/P&gt;
&lt;P&gt;Take the thing you explain to Copilot over and over. Put it in a file with a name, a description, and a set of instructions. Save it. From then on you point Copilot at the skill instead of retyping the prompt, and you get the same result without rebuilding it.&lt;/P&gt;
&lt;P&gt;Monthly business review formatting. Your team's deck standards. The way you like speaker notes written. All of it becomes something you call by name.&lt;/P&gt;
&lt;H2&gt;Two things before you start&lt;/H2&gt;
&lt;P&gt;&lt;STRONG&gt;A Microsoft 365 Copilot license.&lt;/STRONG&gt;&amp;nbsp;Skills live in the Copilot pane inside PowerPoint. No Copilot in your Office apps, no skills.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Choose Your Model.&lt;/STRONG&gt;&amp;nbsp; Open the Copilot pane, you can leave the model to "Auto" or find the model picker, and switch to your preferred GPT or Claude model.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;**Update** Skills in PowerPoint should now work with both OpenAI and Anthrophic models&lt;/STRONG&gt;&lt;/P&gt;
&lt;H2&gt;Turning skills on&lt;/H2&gt;
&lt;P&gt;Open Copilot in PowerPoint. Hit the plus button at the bottom of the pane, then&amp;nbsp;&lt;STRONG&gt;Choose skills&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;You'll already have a few there from Microsoft. Run one before you build anything of your own.&lt;/P&gt;
&lt;P&gt;You can also call a skill by name. Type @ and the skill name in your prompt, the same way you'd mention a person, and Copilot runs that one. Once you know what you have, it beats going through the menu every time.&lt;/P&gt;
&lt;P&gt;I opened&amp;nbsp;&lt;STRONG&gt;Background and context&lt;/STRONG&gt;&amp;nbsp;on a text-heavy slide and asked it to visualize the slide. It created a new slide and generated an image that carried the same information in a format I could read at a glance. Side by side with the original, it wasn't close.&lt;/P&gt;
&lt;H2&gt;Skill plus prompt&lt;/H2&gt;
&lt;P&gt;The image was good, and it was an image, so I couldn't edit any of it.&lt;/P&gt;
&lt;P&gt;So I asked, in plain language: I like this, can you make it more native PowerPoint so I can edit it? Keep the structure.&lt;/P&gt;
&lt;P&gt;It rebuilt the whole thing with real PowerPoint objects and kept the layout that made it work. I wasn't running any branding at that point and it still came out clean.&lt;/P&gt;
&lt;P&gt;Skill first, then prompt. That combination is where most of the value sits. The skill gets you 80 percent of the way with no typing, and the prompt handles the part only you know.&lt;/P&gt;
&lt;H2&gt;Building your own&lt;/H2&gt;
&lt;P&gt;Go back to the plus button,&amp;nbsp;&lt;STRONG&gt;Choose skills&lt;/STRONG&gt;, then&amp;nbsp;&lt;STRONG&gt;Manage skills&lt;/STRONG&gt;. There's a Custom skills section, and it'll be greyed out until you have skills of your own.&lt;/P&gt;
&lt;P&gt;Don't hand-write the skill file.&lt;/P&gt;
&lt;P&gt;Grab Microsoft's documentation page, the one PowerPoint links to from the Manage skills pane:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.microsoft.com/en-us/powerpoint/copilot/copilot-in-powerpoint-skills" target="_blank" rel="noopener"&gt;https://support.microsoft.com/en-us/powerpoint/copilot/copilot-in-powerpoint-skills&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Paste that URL into Copilot and say:&amp;nbsp;&lt;EM&gt;using this link, help me build a PowerPoint skill that does X.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Copilot reads the requirements and writes a file that fits the format. You're using AI to build AI, and it saves you more than typing. Skill files have real formatting rules, and Copilot will meet them instead of you finding each one through a failed upload.&lt;/P&gt;
&lt;P&gt;The format itself is short. A skill is a folder with a&amp;nbsp;SKILL.md&amp;nbsp;file in it. The file opens with a frontmatter block between three-dash delimiters holding a name and a description, and everything below that is your instructions. Spend your time on the description. That's the part telling Copilot when to reach for the skill, so a vague one means it never fires.&lt;/P&gt;
&lt;P&gt;If somebody sent you a skill, paste that in too and let Copilot clean it up.&lt;/P&gt;
&lt;H2&gt;Where skills live&lt;/H2&gt;
&lt;P&gt;In Manage skills, if you've never set this up, you'll see an option to create your skills library. Click it and Copilot creates the folder in your OneDrive.&lt;/P&gt;
&lt;P&gt;Pay attention to the path, because you'll need it:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;OneDrive &amp;gt; Documents &amp;gt; Copilot &amp;gt; Microsoft PowerPoint &amp;gt; skills&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Each skill is its own folder with a&amp;nbsp;SKILL.md&amp;nbsp;file inside. Drop new skills in there and they show up in PowerPoint.&lt;/P&gt;
&lt;P&gt;One catch: after you add something to OneDrive, refresh PowerPoint. It has to reload the folder. If you added a skill and it isn't showing, that's usually why.&lt;/P&gt;
&lt;P&gt;The other one that will bite you is the folder name. It has to match the name inside the&amp;nbsp;SKILL.md&amp;nbsp;file. Copilot skips any folder where those two don't line up, and it skips it quietly. No error, no warning, the skill is missing. If you refreshed and it's still not there, check that next.&lt;/P&gt;
&lt;H2&gt;Two ways to add a skill, and the limit on one of them&lt;/H2&gt;
&lt;P&gt;You don't have to touch OneDrive at all.&lt;/P&gt;
&lt;P&gt;In Manage skills,&amp;nbsp;&lt;STRONG&gt;Add skill&lt;/STRONG&gt;&amp;nbsp;lets you upload an&amp;nbsp;.md&amp;nbsp;file, or type a skill in by hand with a name, description, and instructions. PowerPoint builds the folder structure and the file for you.&lt;/P&gt;
&lt;P&gt;I lost time on this one. The box where you type or paste a skill in caps at 1024 characters. I had Copilot write me a few skills, they came out longer than that, and I got errors that didn't explain themselves. I built them with Copilot, so I assumed they were fine.&lt;/P&gt;
&lt;P&gt;That cap is on the typed box. Uploading an&amp;nbsp;.md&amp;nbsp;file, or dropping the folder straight into OneDrive, doesn't have it. So if you have a long skill, don't cut it down to fit. Upload it as a file instead.&lt;/P&gt;
&lt;H2&gt;Three skills on one bad deck&lt;/H2&gt;
&lt;P&gt;Here's what I have built:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Brand check.&lt;/STRONG&gt;&amp;nbsp;Reviews wording, terminology, and capitalization against our team's deck standards. No layout changes.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Handoff notes.&lt;/STRONG&gt;&amp;nbsp;Writes speaker notes for someone else to deliver. I write the deck knowing I might not be the one presenting it, and my notes are useless to anybody but me.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Slide diet.&lt;/STRONG&gt;&amp;nbsp;Takes a long deck, cuts the fluff, consolidates what's left.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Slide design.&lt;/STRONG&gt;&amp;nbsp;The visual pass.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;I ran three of them on a plain deck, in order.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Brand check&lt;/STRONG&gt;&amp;nbsp;went first. Text only. It consolidated some lines, rewrote a few, and fixed capitalization.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Slide diet&lt;/STRONG&gt;&amp;nbsp;went second. It broke walls of text into bullets and cut what wasn't earning its place. Five bullets beat a paragraph block, and it made that call without being told.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Slide design&lt;/STRONG&gt;&amp;nbsp;went last. This is the one where you sit back and let it work. Black text on white turned into something branded and visual, with the information in an order that reads.&lt;/P&gt;
&lt;P&gt;Three skills, and a deck I didn't want to read became one I'd present.&lt;/P&gt;
&lt;H2&gt;Brand kits&lt;/H2&gt;
&lt;P&gt;One more thing in that same plus menu:&amp;nbsp;&lt;STRONG&gt;Brand&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;A brand kit holds your colors, fonts, and icons. You can build one for yourself, or your organization can publish one for everybody in the tenant. Pair a brand kit with a design skill and decks come out on-brand without anyone checking hex codes by hand.&lt;/P&gt;
&lt;H2&gt;What it cost and what it saved&lt;/H2&gt;
&lt;P&gt;The full run took 30 to 40 minutes, and the design pass was about 10 of that. Copilot needs time to work through a deck. This isn't instant.&lt;/P&gt;
&lt;P&gt;Building that by hand, at the quality it came out at, is 4 to 8 hours. A full day.&lt;/P&gt;
&lt;H2&gt;The documentation&lt;/H2&gt;
&lt;P&gt;Microsoft's page for all of this is here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.microsoft.com/en-us/powerpoint/copilot/copilot-in-powerpoint-skills" target="_blank" rel="noopener"&gt;https://support.microsoft.com/en-us/powerpoint/copilot/copilot-in-powerpoint-skills&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;It has the format requirements, the three ways to add a skill, and how to edit or delete one. Worth a read before you build your second skill.&lt;/P&gt;
&lt;P&gt;One thing that page points to is worth knowing: the SKILL.md format is an open spec, not a PowerPoint invention. So the skills you write here aren't stuck in PowerPoint.&lt;/P&gt;
&lt;H2&gt;Where to start&lt;/H2&gt;
&lt;P&gt;Pick the pattern you repeat most, not the hardest deck you own.&lt;/P&gt;
&lt;P&gt;Write down what you'd tell a new hire about how you do it. That's your first skill. Hand it to Copilot, let it write the file, drop it in the folder, refresh PowerPoint.&lt;/P&gt;
&lt;P&gt;Then be curious, and go push some buttons.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Aug 2026 15:47:53 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/how-to-set-up-copilot-skills-in-powerpoint-and-build-your-own/ba-p/4548273</guid>
      <dc:creator>michaelgoad</dc:creator>
      <dc:date>2026-08-20T15:47:53Z</dc:date>
    </item>
    <item>
      <title>Clinical precision starts with more complete documentation</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/clinical-precision-starts-with-more-complete-documentation/ba-p/4547925</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;This blog is authored by Josh Waldo, Product Manager&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Every patient has a story, and that story deserves to be accurately reflected in the clinical documentation.&lt;/P&gt;
&lt;P&gt;Clinicians work hard to assess, diagnose, and care for patients, often while balancing complex cases, competing priorities, and limited time. While the diagnosis itself may be clear, the documentation does not always capture every detail that helps tell the full patient story. Important clinical information about severity, complexity, acuity, or related conditions may be discussed during the encounter but not fully reflected in the medical record.&lt;/P&gt;
&lt;P&gt;These details matter. Clinical documentation serves as the foundation for communication across care teams, supports quality reporting and care coordination, and provides an accurate record of the care delivered.&lt;/P&gt;
&lt;P&gt;Dragon Copilot helps clinicians create more complete documentation by identifying potential opportunities where additional specificity may be appropriate based on information already present within the encounter. This capability helps ensure that the documentation more fully reflects the clinician's assessment and the patient's clinical story.&lt;/P&gt;
&lt;P&gt;Rather than asking clinicians to remember every documentation requirement or revisit records after the encounter, Dragon Copilot can surface contextual suggestions that highlight where additional detail may strengthen the completeness of the note. For example, when documenting certain conditions, clinicians may receive suggestions that help capture additional clinically relevant details that were discussed during the visit and support a more complete description of the patient's condition.&lt;/P&gt;
&lt;P&gt;Importantly, these suggestions do not change a diagnosis, influence clinical decision-making, or replace clinician judgment. The clinician remains responsible for every diagnosis and every documentation decision. Dragon Copilot simply helps ensure that the documentation accurately reflects what the clinician already knows and has determined.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Supporting better documentation without disrupting workflow&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Documentation quality should not require additional chart reviews, extensive research, or time-consuming follow-up work.&lt;/P&gt;
&lt;P&gt;Dragon Copilot is designed to fit naturally into existing clinical workflows, providing documentation support within the course of the encounter. By surfacing opportunities for greater specificity at the point of documentation, clinicians can address potential gaps in the moment rather than correcting them later.&lt;/P&gt;
&lt;P&gt;This may help reduce the need for downstream clarification requests from CDI and coding teams, saving time while improving the completeness of the medical record.&lt;/P&gt;
&lt;P&gt;Most importantly, clinicians remain in control. Suggestions are simply that suggestions. The clinician decides what is relevant, appropriate, and ultimately included in the note.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Why more complete documentation matters&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Clinical documentation is used by many people beyond the author of the note. Physicians, nurses, specialists, care coordinators, coding professionals, quality teams, and healthcare organizations all rely on documentation to understand a patient's condition and the care that was provided.&lt;/P&gt;
&lt;P&gt;When documentation more fully reflects the clinician's assessment, it can support clearer communication across teams and a more consistent understanding of the patient's clinical status throughout the care journey.&lt;/P&gt;
&lt;P&gt;More complete documentation can also help organizations better reflect patient complexity, support quality initiatives, and reduce the administrative effort associated with documentation clarification and follow-up.&lt;/P&gt;
&lt;P&gt;For clinicians, that means less time spent revisiting notes and more confidence that the patient's story has been accurately captured in the record.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;AI that supports clinical expertise&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Dragon Copilot is built on a simple principle: AI should support clinical expertise, not replace it.&lt;/P&gt;
&lt;P&gt;Diagnosis specificity suggestions is built on a foundation of proven clinical AI innovation, informed by more than a decade of real-world healthcare experience. Drawing on years of clinician interactions and documentation insights, the feature is designed to surface meaningful opportunities for greater diagnostic specificity while fitting naturally into existing workflows.&lt;/P&gt;
&lt;P&gt;The technology does not diagnose patients, recommend treatments, or override clinical judgment. Instead, it acts as an intelligent assistant that helps clinicians identify opportunities to enhance documentation based on information already available during the encounter.&lt;/P&gt;
&lt;P&gt;By reducing some of the cognitive burden associated with documentation, Dragon Copilot allows clinicians to focus their attention where it matters most: caring for patients.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Helping the right patient story reach the medical record&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Healthcare organizations continue to look for ways to improve documentation quality while reducing administrative burden. Achieving both goals requires technology that works alongside clinicians, helping them document care more efficiently without creating additional work.&lt;/P&gt;
&lt;P&gt;By helping clinicians capture greater detail within their existing workflows, Dragon Copilot supports more complete records, more accurate documentation, and a smoother documentation experience.&lt;/P&gt;
&lt;P&gt;Because better documentation is not about changing the diagnosis.&lt;/P&gt;
&lt;P&gt;It is about helping ensure that the right patient story is reflected in the medical record with greater clarity, completeness, and confidence.&lt;/P&gt;
&lt;P&gt;Learn more about &lt;A href="https://www.microsoft.com/en-us/health-solutions/clinical-workflow/dragon-copilot" target="_blank" rel="noopener"&gt;Dragon Copilot&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Aug 2026 20:52:04 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/clinical-precision-starts-with-more-complete-documentation/ba-p/4547925</guid>
      <dc:creator>Karen_Couchon</dc:creator>
      <dc:date>2026-08-18T20:52:04Z</dc:date>
    </item>
    <item>
      <title>Amplify Healthcare Intelligence: Data, AI, and Agent-Powered Transformation</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/amplify-healthcare-intelligence-data-ai-and-agent-powered/ba-p/4542939</link>
      <description>&lt;P&gt;Join Microsoft for &lt;STRONG&gt;Amplify Healthcare Intelligence&lt;/STRONG&gt;, a webinar and in-person workshop series designed for healthcare and life sciences organizations building the foundation for trusted AI. Every session starts from the same premise: you cannot deliver trusted AI without a trusted data foundation. Across the series you will see how leading organizations unify their data estate, ground AI agents in real business context, and turn that foundation into results they can measure.&lt;/P&gt;
&lt;H5&gt;What You Will Learn&lt;/H5&gt;
&lt;UL&gt;
&lt;LI&gt;How to build a unified, AI-ready data foundation across a fragmented healthcare data estate&lt;/LI&gt;
&lt;LI&gt;How to ground AI agents in trusted healthcare data and real business context&lt;/LI&gt;
&lt;LI&gt;How to modernize analytics while reducing complexity and cost&lt;/LI&gt;
&lt;LI&gt;How to accelerate innovation with Microsoft Fabric, Azure AI Foundry, Microsoft IQ, and Copilot technologies&lt;/LI&gt;
&lt;LI&gt;How to deliver measurable impact across clinical, operational, research, and business scenarios&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Whether you are defining your AI strategy, modernizing your analytics platform, or scaling AI across your organization, these sessions offer practical guidance, real-world customer examples, and hands-on learning to help you move from AI ambition to business impact.&lt;/P&gt;
&lt;H3&gt;Webinars &amp;amp; In-Person Workshops&lt;/H3&gt;
&lt;H4&gt;🎥 Webinars&lt;/H4&gt;
&lt;P&gt;One-hour virtual sessions with actionable guidance, live demonstrations, customer stories, and best practices from Microsoft experts. Each webinar shows how leading healthcare organizations are turning data, AI, and enterprise intelligence into measurable business outcomes. All sessions are from 3-4 ET (12-1 PT) and are free to attend.&lt;/P&gt;
&lt;DIV class="styles_lia-table-wrapper__h6Xo9 styles_table-responsive__MW0lN"&gt;&lt;table border="1" style="width: 61.2956%; height: 492.116px; border-width: 1px;"&gt;&lt;thead&gt;&lt;tr style="height: 34.7107px;"&gt;&lt;th style="height: 34.7107px;"&gt;Date&lt;/th&gt;&lt;th style="height: 34.7107px;"&gt;Topic&lt;/th&gt;&lt;th style="height: 34.7107px;"&gt;Register&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr style="height: 95.681px;"&gt;&lt;td style="height: 95.681px;"&gt;
&lt;P&gt;&lt;STRONG&gt;Oct 28&lt;BR /&gt;&lt;/STRONG&gt;3-4 ET (12-1 PT)&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td style="height: 95.681px;"&gt;
&lt;P&gt;&lt;STRONG&gt;Reduce BI Sprawl, Cut Cost and Build an AI-Ready Analytics Foundation&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td style="height: 95.681px;"&gt;
&lt;P&gt;&lt;A class="lia-external-url" href="https://msit.events.teams.microsoft.com/event/msit.b6035267-ef74-452e-808b-43b497c41191@72f988bf-86f1-41af-91ab-2d7cd011db47" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 92.6852px;"&gt;&lt;td style="height: 92.6852px;"&gt;
&lt;P&gt;&lt;STRONG&gt;Nov 11&lt;BR /&gt;&lt;/STRONG&gt;3-4 ET (12-1 PT)&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td style="height: 92.6852px;"&gt;
&lt;P&gt;&lt;STRONG&gt;Connecting Microsoft Fabric with ExpressRoute: Enterprise Network Architecture&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td style="height: 92.6852px;"&gt;
&lt;P&gt;&lt;A class="lia-external-url" href="https://msit.events.teams.microsoft.com/event/msit.60ff6d18-3e4e-41f9-81e8-eace24e35d2b@72f988bf-86f1-41af-91ab-2d7cd011db47" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 89.6759px;"&gt;&lt;td style="height: 89.6759px;"&gt;
&lt;P&gt;&lt;STRONG&gt;Nov 18&lt;BR /&gt;&lt;/STRONG&gt;3-4 ET (12-1 PT)&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td style="height: 89.6759px;"&gt;
&lt;P&gt;&lt;STRONG&gt;From Question to Visuals: Data Insights with Fabric, Rayfin &amp;amp; GitHub Copilot​&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td style="height: 89.6759px;"&gt;
&lt;P&gt;&lt;A class="lia-external-url" href="https://msit.events.teams.microsoft.com/event/msit.e10596ad-2886-405c-90e2-20e318120bf0@72f988bf-86f1-41af-91ab-2d7cd011db47" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 93.6806px;"&gt;&lt;td style="height: 93.6806px;"&gt;
&lt;P&gt;&lt;STRONG&gt;Dec 2&lt;BR /&gt;&lt;/STRONG&gt;3-4 ET (12-1 PT)&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td style="height: 93.6806px;"&gt;
&lt;P&gt;&lt;STRONG&gt;The Intelligent Healthcare Enterprise: Microsoft IQ in Action&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td style="height: 93.6806px;"&gt;
&lt;P&gt;&lt;A class="lia-external-url" href="https://msit.events.teams.microsoft.com/event/msit.f1ccfec8-7c9d-4407-980f-dcffe877a23d@72f988bf-86f1-41af-91ab-2d7cd011db47" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 85.6829px;"&gt;&lt;td style="height: 85.6829px;"&gt;
&lt;P&gt;&lt;STRONG&gt;Dec 9&lt;BR /&gt;&lt;/STRONG&gt;3-4 ET (12-1 PT)&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td style="height: 85.6829px;"&gt;
&lt;P&gt;&lt;STRONG&gt;From Trusted Data to Action: Microsoft Fabric + Copilot Cowork for Healthcare &amp;amp; Life Sciences&lt;/STRONG&gt;&lt;/P&gt;
&lt;/td&gt;&lt;td style="height: 85.6829px;"&gt;
&lt;P&gt;&lt;A class="lia-external-url" href="https://msit.events.teams.microsoft.com/event/msit.47dd4f9b-6b9f-4565-9f26-f50feef1da91@72f988bf-86f1-41af-91ab-2d7cd011db47" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/P&gt;
&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;colgroup&gt;&lt;col style="width: 22.0794%" /&gt;&lt;col style="width: 58.0689%" /&gt;&lt;col style="width: 19.8139%" /&gt;&lt;/colgroup&gt;&lt;/table&gt;&lt;/DIV&gt;
&lt;P&gt;Cannot join live? Register anyway. We will send you the recording and session materials after the event. Additional sessions will be added through the end of the year, so check back or register for one session to be notified as new dates are announced.&lt;/P&gt;
&lt;H4&gt;🏢 In-Person Workshops&lt;/H4&gt;
&lt;P&gt;Our two-day workshops combine executive strategy, healthcare-specific use cases, architecture guidance, and hands-on labs designed to help teams identify and accelerate high-value AI opportunities. Attendance is free. Participants are responsible for their own travel and accommodation, and space at each location is limited. Workshops run 9am to 4pm local time on both days.&lt;/P&gt;
&lt;H5&gt;&lt;STRONG&gt;Day 1: From Healthcare Data to Healthcare Intelligence&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;Day 1 focuses on healthcare transformation strategy, customer examples, and the architectural patterns that make trusted AI possible at scale. The day closes with a networking reception and peer exchange.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The Frontier Transformation imperative: from AI ambition to measurable impact&lt;/LI&gt;
&lt;LI&gt;Microsoft IQ: turning data into enterprise intelligence&lt;/LI&gt;
&lt;LI&gt;Building the unified data foundation&lt;/LI&gt;
&lt;LI&gt;Building trusted AI: security, governance, privacy, and compliance&lt;/LI&gt;
&lt;LI&gt;Healthcare transformation in action: clinical, operational, research, and finance scenarios&lt;/LI&gt;
&lt;LI&gt;Activating data with AI data agents and Copilot experiences&lt;/LI&gt;
&lt;/UL&gt;
&lt;H5&gt;&lt;STRONG&gt;Day 2: Hands-On Healthcare AI and Analytics Lab&lt;/STRONG&gt;&lt;/H5&gt;
&lt;P&gt;Day 2 is a guided, end-to-end lab. Participants build a working healthcare intelligence solution from raw data through to a grounded AI agent, using Microsoft Fabric, Azure AI Foundry, Copilot technologies, and modern data architectures.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Build the foundation: data ingestion, lakehouse architecture, and data engineering&lt;/LI&gt;
&lt;LI&gt;Create actionable insights: semantic models and dashboards&lt;/LI&gt;
&lt;LI&gt;Prepare data for AI: AI-ready data assets and data governance&lt;/LI&gt;
&lt;LI&gt;Build and ground AI agents in trusted enterprise data&lt;/LI&gt;
&lt;LI&gt;From insight to intelligent action: planning your organization's next steps&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;What to bring: a laptop with a current browser. Lab environments and credentials are provided on site, and no prior Fabric or Foundry experience is assumed.&amp;nbsp;&lt;/P&gt;
&lt;DIV class="styles_lia-table-wrapper__h6Xo9 styles_table-responsive__MW0lN"&gt;&lt;table border="1" style="width: 74.9992%; height: 231.097px; border-width: 1px;"&gt;&lt;thead&gt;&lt;tr style="height: 34.7107px;"&gt;&lt;th style="height: 34.7107px;"&gt;Date&lt;/th&gt;&lt;th style="height: 34.7107px;"&gt;City&lt;/th&gt;&lt;th style="height: 34.7107px;"&gt;Venue&lt;/th&gt;&lt;th style="height: 34.7107px;"&gt;Register&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr style="height: 94.6968px;"&gt;&lt;td style="height: 94.6968px;"&gt;&lt;STRONG&gt;November 10-11, 2026&lt;BR /&gt;&lt;/STRONG&gt;9am - 4pm&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 94.6968px;"&gt;&lt;STRONG&gt;Chicago&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 94.6968px;"&gt;Microsoft Chicago (AON Center)&lt;BR /&gt;200 East Randolph Drive, Suite 200&lt;BR /&gt;Chicago, IL 60601&lt;/td&gt;&lt;td style="height: 94.6968px;"&gt;&lt;A class="lia-external-url" href="https://forms.cloud.microsoft/r/kUB3YTtL3T" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 101.69px;"&gt;&lt;td style="height: 101.69px;"&gt;&lt;STRONG&gt;December 8-9, 2026&lt;BR /&gt;&lt;/STRONG&gt;9am - 4pm&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 101.69px;"&gt;&lt;STRONG&gt;New York&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 101.69px;"&gt;Microsoft Garage&lt;BR /&gt;300 Lafayette Street&lt;BR /&gt;New York, NY 10012&lt;/td&gt;&lt;td style="height: 101.69px;"&gt;&lt;A class="lia-external-url" href="https://forms.cloud.microsoft/r/kUB3YTtL3T" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;colgroup&gt;&lt;col style="width: 27.4329%" /&gt;&lt;col style="width: 17.1764%" /&gt;&lt;col style="width: 35.8321%" /&gt;&lt;col style="width: 19.528%" /&gt;&lt;/colgroup&gt;&lt;/table&gt;&lt;/DIV&gt;
&lt;DIV class="styles_lia-table-wrapper__h6Xo9 styles_table-responsive__MW0lN"&gt;
&lt;H4&gt;Who Should Attend&lt;/H4&gt;
&lt;P&gt;This series is built for the people who own the data estate and the people who depend on it. Sessions are technical enough for practitioners and strategic enough for the leaders who prioritize the work.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Data &amp;amp; analytics leaders&lt;/LI&gt;
&lt;LI&gt;Data platform, data engineering, and business intelligence teams&lt;/LI&gt;
&lt;LI&gt;Data architects, engineers, and data scientists&lt;/LI&gt;
&lt;LI&gt;AI and innovation leaders&lt;/LI&gt;
&lt;LI&gt;Healthcare and life sciences executives&lt;/LI&gt;
&lt;LI&gt;Clinical, operational, research, and finance transformation leaders&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;No prior Microsoft Fabric or AI experience is required for any session in this series.&lt;/P&gt;
&lt;H4&gt;Questions&lt;/H4&gt;
&lt;P&gt;Contact&amp;nbsp;&lt;A class="lia-external-url" href="mailto:cawhicke@microsoft.com" target="_blank" rel="noopener"&gt;Camille Whicker&lt;/A&gt; if you have any questions about our upcoming events.&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 27 Oct 2026 03:17:53 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/amplify-healthcare-intelligence-data-ai-and-agent-powered/ba-p/4542939</guid>
      <dc:creator>CamilleWhicker</dc:creator>
      <dc:date>2026-10-27T03:17:53Z</dc:date>
    </item>
    <item>
      <title>Amplify Healthcare Intelligence In-Person Workshop Series</title>
      <link>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/amplify-healthcare-intelligence-in-person-workshop-series/ba-p/4543028</link>
      <description>&lt;H3&gt;What You'll Learn&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;How leading organizations are navigating the Frontier Transformation journey&lt;/LI&gt;
&lt;LI&gt;Strategies for turning healthcare data, workflows, and expertise into organizational intelligence&lt;/LI&gt;
&lt;LI&gt;Best practices for building a unified, AI-ready data foundation&lt;/LI&gt;
&lt;LI&gt;Approaches for implementing trusted AI with strong governance and security&lt;/LI&gt;
&lt;LI&gt;Real-world healthcare scenarios across clinical, operational, financial, and research domains&lt;/LI&gt;
&lt;LI&gt;How AI agents can transform the way people interact with data and make decisions&lt;/LI&gt;
&lt;LI&gt;Practical skills for deploying analytics, AI, and agent-powered solutions&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;Day 1: From Healthcare Data to Healthcare Intelligence&lt;/H3&gt;
&lt;P&gt;Explore how leading healthcare organizations are creating a trusted foundation for AI and transforming data into meaningful business outcomes.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;The Frontier Transformation Imperative&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The future of healthcare in the age of AI and agents&lt;/LI&gt;
&lt;LI&gt;Industry trends, opportunities, and challenges&lt;/LI&gt;
&lt;LI&gt;Moving from AI ambition to measurable impact&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Microsoft IQ: Turning Data into Enterprise Intelligence&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Connecting data, workflows, and organizational knowledge&lt;/LI&gt;
&lt;LI&gt;Building organizational intelligence for AI&lt;/LI&gt;
&lt;LI&gt;Establishing the foundation for trusted decision-making&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Building the Unified Data Foundation&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Modernizing the healthcare data estate&lt;/LI&gt;
&lt;LI&gt;Creating a single source of truth for analytics and AI&lt;/LI&gt;
&lt;LI&gt;Leveraging Microsoft Fabric and OneLake as a unified platform&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Building Trusted AI&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Security, governance, privacy, and compliance&lt;/LI&gt;
&lt;LI&gt;Responsible AI considerations for healthcare and life sciences&lt;/LI&gt;
&lt;LI&gt;Preparing data and processes for enterprise AI adoption&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Healthcare Transformation in Action&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Clinical transformation scenarios&lt;/LI&gt;
&lt;LI&gt;Operational transformation scenarios&lt;/LI&gt;
&lt;LI&gt;Research and innovation use cases&lt;/LI&gt;
&lt;LI&gt;Finance and performance management opportunities&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Activating Data with AI Agents&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;AI Data Agents and Copilot experiences&lt;/LI&gt;
&lt;LI&gt;From data to decision-making&lt;/LI&gt;
&lt;LI&gt;Real-world examples of agent-powered healthcare innovation&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Networking Reception &amp;amp; Peer Exchange&lt;/STRONG&gt;&lt;/P&gt;
&lt;H3&gt;Day 2: Hands-On Healthcare AI &amp;amp; Analytics Lab&lt;/H3&gt;
&lt;P&gt;Gain practical experience building an end-to-end healthcare intelligence solution using Microsoft technologies.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Build the Foundation&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Data ingestion and modernization patterns&lt;/LI&gt;
&lt;LI&gt;Lakehouse architecture and data engineering&lt;/LI&gt;
&lt;LI&gt;Establishing a scalable healthcare data platform&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Create Actionable Insights&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Semantic models and business intelligence&lt;/LI&gt;
&lt;LI&gt;Power BI dashboards and reporting&lt;/LI&gt;
&lt;LI&gt;Real-time healthcare intelligence&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Prepare Data for AI&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Building AI-ready data assets&lt;/LI&gt;
&lt;LI&gt;Data governance and trust&lt;/LI&gt;
&lt;LI&gt;Optimizing data for intelligent applications&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;Build and Ground AI Agents&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Creating AI Data Agents&lt;/LI&gt;
&lt;LI&gt;Leveraging business context and trusted enterprise data&lt;/LI&gt;
&lt;LI&gt;Connecting agents to analytics and operational workflows&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG&gt;From Insight to Intelligent Action&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;End-to-end healthcare AI scenario&lt;/LI&gt;
&lt;LI&gt;Data → Insights → Agents → Outcomes&lt;/LI&gt;
&lt;LI&gt;Planning your organization's next steps&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;Upcoming Workshop Locations&lt;/H3&gt;
&lt;DIV class="styles_lia-table-wrapper__h6Xo9 styles_table-responsive__MW0lN"&gt;&lt;table border="1" style="width: 69.537%; height: 626.864px; border-width: 1px;"&gt;&lt;thead&gt;&lt;tr style="height: 34.7107px;"&gt;&lt;th style="height: 34.7107px;"&gt;Date&lt;/th&gt;&lt;th style="height: 34.7107px;"&gt;City&lt;/th&gt;&lt;th style="height: 34.7107px;"&gt;Venue&lt;/th&gt;&lt;th style="height: 34.7107px;"&gt;Register&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr style="height: 82.6968px;"&gt;&lt;td style="height: 82.6968px;"&gt;&lt;STRONG&gt;September 9-10, 2026&lt;BR /&gt;&lt;/STRONG&gt;9am - 4pm&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 82.6968px;"&gt;&lt;STRONG&gt;Dallas&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 82.6968px;"&gt;Microsoft Las Colinas 1&lt;BR /&gt;7000 N State Hwy 161&lt;BR /&gt;Irving, TX 75039&lt;/td&gt;&lt;td style="height: 82.6968px;"&gt;&lt;A class="lia-external-url" href="https://forms.cloud.microsoft/r/kUB3YTtL3T" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 106.69px;"&gt;&lt;td style="height: 106.69px;"&gt;&lt;STRONG&gt;September 29-30, 2026&lt;BR /&gt;&lt;/STRONG&gt;9am - 4pm&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 106.69px;"&gt;&lt;STRONG&gt;Minneapolis&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 106.69px;"&gt;Microsoft Edina&lt;BR /&gt;3601 West 76th Street, Suite 600&lt;BR /&gt;Edina, MN 55435&lt;/td&gt;&lt;td style="height: 106.69px;"&gt;&lt;A class="lia-external-url" href="https://forms.cloud.microsoft/r/kUB3YTtL3T" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 82.6968px;"&gt;&lt;td style="height: 82.6968px;"&gt;&lt;STRONG&gt;October 13-14, 2026&lt;BR /&gt;&lt;/STRONG&gt;9am - 4pm&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 82.6968px;"&gt;&lt;STRONG&gt;Boston&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 82.6968px;"&gt;Microsoft New England&lt;BR /&gt;One Memorial Drive&lt;BR /&gt;Cambridge, MA 02142&lt;/td&gt;&lt;td style="height: 82.6968px;"&gt;&lt;A class="lia-external-url" href="https://forms.cloud.microsoft/r/kUB3YTtL3T" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 106.69px;"&gt;&lt;td style="height: 106.69px;"&gt;&lt;STRONG&gt;October 27-28, 2026&lt;BR /&gt;&lt;/STRONG&gt;9am - 4pm&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 106.69px;"&gt;&lt;STRONG&gt;Silicon Valley&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 106.69px;"&gt;Microsoft Silicon Valley&lt;BR /&gt;1045 La Avenida Street&lt;BR /&gt;Mountain View, CA 94043&lt;/td&gt;&lt;td style="height: 106.69px;"&gt;&lt;A class="lia-external-url" href="https://forms.cloud.microsoft/r/kUB3YTtL3T" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 130.683px;"&gt;&lt;td style="height: 130.683px;"&gt;&lt;STRONG&gt;November 10-11, 2026&lt;BR /&gt;&lt;/STRONG&gt;9am - 4pm&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 130.683px;"&gt;&lt;STRONG&gt;Chicago&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 130.683px;"&gt;Microsoft Chicago (AON Center)&lt;BR /&gt;200 East Randolph Drive, Suite 200&lt;BR /&gt;Chicago, IL 60601&lt;/td&gt;&lt;td style="height: 130.683px;"&gt;&lt;A class="lia-external-url" href="https://forms.cloud.microsoft/r/kUB3YTtL3T" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr style="height: 82.6968px;"&gt;&lt;td style="height: 82.6968px;"&gt;&lt;STRONG&gt;December 8-9, 2026&lt;BR /&gt;&lt;/STRONG&gt;9am - 4pm&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 82.6968px;"&gt;&lt;STRONG&gt;New York&lt;/STRONG&gt;&lt;/td&gt;&lt;td style="height: 82.6968px;"&gt;Microsoft Garage&lt;BR /&gt;300 Lafayette Street&lt;BR /&gt;New York, NY 10012&lt;/td&gt;&lt;td style="height: 82.6968px;"&gt;&lt;A class="lia-external-url" href="https://forms.cloud.microsoft/r/kUB3YTtL3T" target="_blank" rel="noopener"&gt;Register&lt;/A&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;colgroup&gt;&lt;col style="width: 25.00%" /&gt;&lt;col style="width: 25.00%" /&gt;&lt;col style="width: 25.00%" /&gt;&lt;col style="width: 25.00%" /&gt;&lt;/colgroup&gt;&lt;/table&gt;&lt;/DIV&gt;
&lt;H3&gt;Who Should Attend?&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;Healthcare and Life Sciences Executives&lt;/LI&gt;
&lt;LI&gt;CIOs, CTOs, and Chief Data Officers&lt;/LI&gt;
&lt;LI&gt;Clinical and Operational Leaders&lt;/LI&gt;
&lt;LI&gt;Analytics and Data Platform Teams&lt;/LI&gt;
&lt;LI&gt;AI and Innovation Leaders&lt;/LI&gt;
&lt;LI&gt;Finance Transformation Teams&lt;/LI&gt;
&lt;LI&gt;Architects, Engineers, and Data Professionals&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;What You'll Walk Away With&lt;/H3&gt;
&lt;P&gt;By the end of the workshop, you'll have a clear understanding of how to build a unified data and AI foundation, enable trusted AI and intelligent agents, and create a roadmap for accelerating healthcare transformation within your organization.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Aug 2026 18:29:53 GMT</pubDate>
      <guid>https://techcommunity.microsoft.com/t5/healthcare-and-life-sciences/amplify-healthcare-intelligence-in-person-workshop-series/ba-p/4543028</guid>
      <dc:creator>CamilleWhicker</dc:creator>
      <dc:date>2026-08-20T18:29:53Z</dc:date>
    </item>
  </channel>
</rss>

