|
| 1 | +--- |
| 2 | +title: Outbound Access Protection for Operations Agent (Preview) |
| 3 | +description: Learn how workspace outbound access protection governs the outbound actions an operations agent can take, and what's supported during outbound access protection for operations agent preview. |
| 4 | +author: baanders |
| 5 | +ms.author: baanders |
| 6 | +ms.reviewer: bisiadele |
| 7 | +ms.topic: concept-article |
| 8 | +ms.date: 06/17/2026 |
| 9 | +ai-usage: ai-assisted |
| 10 | +#customer intent: As a workspace admin or operations agent creator, I want to understand how workspace outbound access protection affects an operations agent so that I can keep the agent working while my workspace is locked down. |
| 11 | +--- |
| 12 | + |
| 13 | +# Workspace outbound access protection for operations agent (preview) |
| 14 | + |
| 15 | +[Workspace outbound access protection (OAP)](workspace-outbound-access-protection-overview.md) is a Microsoft Fabric workspace security feature that lets workspace admins control which outbound network connections that items in the workspace can make. When you enable OAP on a workspace that contains an [operations agent](../real-time-intelligence/operations-agent.md), the workspace's connection policy governs the agent's outbound actions. |
| 16 | + |
| 17 | +If your workspace runs an operations agent and has OAP turned on, OAP blocks some of the agent's actions, such as Teams notifications, Power Automate flows, and cross-workspace actions, unless the admin explicitly allows them. During preview, extra limitations apply that affect which actions you can permit. |
| 18 | + |
| 19 | +This article explains what OAP covers for operations agent during preview and what you see when the protection blocks an action. |
| 20 | + |
| 21 | +> [!IMPORTANT] |
| 22 | +> Operations agent is generally available. Support for operations agent with workspace OAP is in preview. The capabilities and limitations described here apply while support for operations agent is in preview. |
| 23 | +
|
| 24 | +## What outbound access protection covers |
| 25 | + |
| 26 | +When you enable OAP on a workspace that contains an operations agent, the policy governs the following outbound actions. |
| 27 | + |
| 28 | +| Capability | Governed by OAP? | Notes | |
| 29 | +|---|---|---| |
| 30 | +| Teams notifications the agent sends | Yes | The agent checks the workspace OAP policy before sending. | |
| 31 | +| Power Automate flows the agent triggers | Yes | Enforced when the [Activator](../real-time-intelligence/data-activator/activator-introduction.md) action runs. Not available during preview (for recommendations, see [Preview limitations](#preview-limitations)). | |
| 32 | +| Fabric jobs in a different workspace | Yes | Enforced when the Activator action runs. Not available during preview (for recommendations, see [Preview limitations](#preview-limitations)). | |
| 33 | +| Fabric actions in the same workspace as the agent | No | Internal to the workspace. | |
| 34 | +| Large language model (LLM) reasoning calls | No | The tenant-level LLM setting governs these calls. | |
| 35 | +| Agent rule evaluation and internal telemetry | No | Internal to Fabric. | |
| 36 | + |
| 37 | +OAP affects only the final outbound execution step. The agent's reasoning, rules, and internal logging continue to operate normally. |
| 38 | + |
| 39 | +## Preview limitations |
| 40 | + |
| 41 | +Plan around the following limitations while operations agent with workspace OAP is in preview. |
| 42 | + |
| 43 | +### Cross-workspace actions aren't supported |
| 44 | + |
| 45 | +Preview supports only in-workspace scenarios. OAP blocks outbound actions that target a different workspace. |
| 46 | + |
| 47 | +**Recommendation:** Keep the agent and its action targets, such as Activator items and other Fabric items, in the same workspace. |
| 48 | + |
| 49 | +### Power Automate actions are blocked |
| 50 | + |
| 51 | +Currently there's no per-workspace toggle for Power Automate. While OAP is on, it blocks [Power Automate actions](../real-time-intelligence/operations-agent-actions.md#configure-a-power-automate-action) that the agent triggers. |
| 52 | + |
| 53 | +**Recommendation:** If your agent depends on Power Automate, keep OAP turned off on that workspace until the toggle ships, or replace the action with a Teams notification or an in-workspace Fabric job. |
| 54 | + |
| 55 | +### Other Fabric item outbound actions are blocked |
| 56 | + |
| 57 | +Per-workspace control for other Fabric item outbound actions isn't currently available. At this time, if OAP is on and you don't explicitly allow the required connection policies, Fabric blocks those actions. |
| 58 | + |
| 59 | +### Connectors without an outbound access protection toggle are blocked |
| 60 | + |
| 61 | +Workspace rules can allow only connectors that explicitly support workspace OAP policy. Fabric blocks any other outbound connector while OAP is on. |
| 62 | + |
| 63 | +### Teams notification delivery depends on the tenant Teams setting |
| 64 | + |
| 65 | +The agent sends Teams notifications directly. Its behavior depends on the [tenant level admin setting](../admin/tenant-settings-index.md) for Teams: |
| 66 | + |
| 67 | +- **Teams allowed in the tenant settings**: When OAP blocks an action, the agent sends a Teams card to the agent creator that explains the block. |
| 68 | +- **Teams not allowed in the tenant settings**: The agent doesn't send a Teams card. Use the Activity Log (see [Monitoring and troubleshooting section](#monitoring-and-troubleshooting)) to verify agent activity and delivery outcomes, including when OAP policies affect operations or block related messaging actions. |
| 69 | + |
| 70 | +### No programmatic bypass |
| 71 | + |
| 72 | +Fabric enforces OAP at the API layer. There's no supported way to bypass workspace OAP from code, scripts, or external API calls. |
| 73 | + |
| 74 | +Use the Activity Log to verify agent activity and delivery outcomes, including when Outbound Access Protection (OAP) policies affect operations or block related messaging actions. |
| 75 | + |
| 76 | +## What you see when an action is blocked |
| 77 | + |
| 78 | +The operations agent doesn't fail silently. When OAP blocks an outbound action, the agent surfaces it as follows. |
| 79 | + |
| 80 | +### In the operations agent UI |
| 81 | + |
| 82 | +A banner appears at the top of the agent window with the following text: |
| 83 | + |
| 84 | +*Limited agent functionality — This workspace has outbound access restrictions that may block some agent actions or notifications.* |
| 85 | + |
| 86 | +:::image type="content" source="media/workspace-outbound-access-protection-operations-agent/error-banner.png" alt-text="Screenshot of the error banner." lightbox="media/workspace-outbound-access-protection-operations-agent/error-banner.png"::: |
| 87 | + |
| 88 | +### In Microsoft Teams (when Teams is allowed) |
| 89 | + |
| 90 | +The agent creator receives a Teams card. |
| 91 | + |
| 92 | +## Settings that affect operations agent |
| 93 | + |
| 94 | +The following settings determine how OAP interacts with an operations agent. |
| 95 | + |
| 96 | +| Setting | Who controls it | Effect on the agent | |
| 97 | +|---|---|---| |
| 98 | +| Workspace OAP policy | Workspace admin | Determines which outbound connections the agent can use. | |
| 99 | +| Teams tenant setting | Tenant admin | Determines whether Teams delivers blocked-action notifications. When off, the agent falls back to the in-app banner. | |
| 100 | +| LLM enablement | Tenant admin | Governs LLM calls. OAP doesn't change this behavior. | |
| 101 | + |
| 102 | +If the agent behaves unexpectedly after OAP is enabled, ask the workspace admin to review the workspace's allowed connections and confirm that it explicitly permits the connectors the agent depends on. |
| 103 | + |
| 104 | +## Monitoring and troubleshooting |
| 105 | + |
| 106 | +Use Activity Log to monitor OAP. |
| 107 | + |
| 108 | +The Activity Log provides visibility into operations agent activities, including how OAP affects agent operations. |
| 109 | + |
| 110 | +To access the Activity Log: |
| 111 | +1. Open your operations agent in Fabric. |
| 112 | +1. In the left navigation pane, under your agent name, select **Activity Log**. |
| 113 | + |
| 114 | +Look for these items in the Activity Log: |
| 115 | +* Blocked outbound requests: Entries showing operations that OAP policies blocked. |
| 116 | +* Failed actions: Check if failures correlate with OAP restrictions. |
| 117 | +* Timestamps: Correlate agent activity with expected behavior. |
| 118 | + |
| 119 | +## Frequently asked questions |
| 120 | + |
| 121 | +This section contains common questions about how OAP affects the operations agent during preview. |
| 122 | + |
| 123 | +### Will my agent stop working as soon as my admin enables outbound access protection? |
| 124 | + |
| 125 | +No. The agent's reasoning, rules, and internal logging continue to operate. OAP blocks only outbound actions that aren't on the workspace allowlist. The agent surfaces those blocks through a banner and, when available, a Teams notification. |
| 126 | + |
| 127 | +### Can I use operations agent without outbound access protection? |
| 128 | + |
| 129 | +Yes. Operations agent is generally available and works without OAP. Enabling OAP is a workspace admin decision. If OAP isn't on for the workspace, none of the preview limitations described here apply. |
| 130 | + |
| 131 | +### Does outbound access protection affect what data the agent reasons over or sends to the LLM? |
| 132 | + |
| 133 | +No. The tenant-level LLM setting governs LLM calls, not workspace OAP. OAP doesn't affect the agent's reasoning step. |
| 134 | + |
| 135 | +### Why does Power Automate get blocked even if it's the only connector the agent uses? |
| 136 | + |
| 137 | +Power Automate doesn't currently have its own OAP toggle for operations agent. While OAP is on, it blocks Power Automate actions. At this time, keep OAP off on workspaces that depend on Power Automate, or substitute a Teams notification. |
| 138 | + |
| 139 | +### My action targets a Fabric item. Does it work? |
| 140 | + |
| 141 | +When the target is in the same workspace as the agent, yes. OAP doesn't apply. When the target is in a different workspace, OAP blocks the action during preview. |
| 142 | + |
| 143 | +### Who sees the blocked-action Teams card? |
| 144 | + |
| 145 | +The agent creator. |
| 146 | + |
| 147 | +### Can I test outbound access protection behavior with operations agent before turning it on in production? |
| 148 | + |
| 149 | +Yes, test in a nonproduction workspace first. Enable OAP, exercise each agent action, and confirm that both the banner and the Teams card render the way you expect for your tenant's Teams configuration. |
| 150 | + |
| 151 | +### What happens to actions that are running when the admin turns on outbound access protection? |
| 152 | + |
| 153 | +OAP evaluates new action attempts against the current policy. If it blocks an attempt, the agent surfaces the block through the standard fallback banner or a Teams card. |
| 154 | + |
| 155 | +### Can I appeal or override a block? |
| 156 | + |
| 157 | +No. There's no programmatic override. To allow a blocked outbound path, the workspace admin needs to add the relevant connection to the workspace's allowlist. |
| 158 | + |
| 159 | +### Where can I follow what's coming next? |
| 160 | + |
| 161 | +Watch your Fabric admin update channels and the [operations agent documentation](../real-time-intelligence/operations-agent.md) for announcements as more features roll out. |
| 162 | + |
| 163 | +## Where to get help |
| 164 | + |
| 165 | +For help with... |
| 166 | +- Workspace allowlists and OAP policy: Contact your Fabric workspace admin. |
| 167 | +- Tenant-level Teams or LLM settings: Contact your Microsoft 365 or Fabric tenant admin. |
| 168 | +- Product issues or feedback: Submit through your standard Microsoft support channel. |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments