Internet Access web content filtering

This page's changes and edits · All guidance changes

Microsoft's edit · 21 Jul 18:04 UTC

Update source traffic type: replace Non-agent with User

Microsoft's commit message in MicrosoftDocs/entra-docs · commit 2ee6ce1 · +6 −6 lines · also on GitHub

⋯ 18 unchanged lines

1919

2020 Web content filtering also supports two optional rule conditions that enable traffic-aware policy enforcement:

2121

22 −- **Source traffic type filtering (preview)**: Scope rules to specific traffic types, either agent or non-agent.

22 +- **Source traffic type filtering (preview)**: Scope rules to specific traffic types, either agent or user.

2323 - **HTTP method request filtering (preview)**: Block or allow specific HTTP methods, such as GET, POST, PUT, PATCH, and DELETE.

2424

2525 > [!TIP]

⋯ 47 unchanged lines

7373

7474 ## Configure source traffic type filtering (preview)

7575

76 −Source traffic type filtering lets you scope web content filtering rules to specific types of network traffic. You can enforce differentiated policies based on whether traffic originates from an AI agent or a non-agent source.

76 +Source traffic type filtering lets you scope web content filtering rules to specific types of network traffic. You can enforce differentiated policies based on whether traffic originates from an AI agent or a user.

7777

7878 ### Supported source traffic types

7979

8080 | Source type | Description |

8181 | --- | --- |

8282 | Agent | Traffic that originates from AI agents, such as Copilot agents or autonomous AI tools. |

83 −| Non-agent | Traffic that originates from any source other than an AI agent, such as web browsers and applications. |

83 +| User | Traffic that originates from a user, such as web browsers and applications. |

8484

8585 ### Configure the source traffic type condition

8686

⋯ 5 unchanged lines

9292 > Source traffic type filtering is available only for client-based Global Secure Access connections. This capability depends on the Global Secure Access client sending task and processor metadata to classify traffic. Remote networks don't support source traffic type rules.

9393

9494 > [!NOTE]

95 −> When a request doesn't originate from an AI agent, traffic is classified as **Non-agent**. To match this traffic, explicitly target **Non-agent** in a rule.

95 +> When a request doesn't originate from an AI agent, traffic is classified as **User**. To match this traffic, explicitly target **User** in a rule.

9696

9797 ### Example: Block AI agents from accessing social networking sites

9898

99 −To prevent AI agents from accessing social networking websites while allowing non-agent traffic:

99 +To prevent AI agents from accessing social networking websites while allowing user traffic:

100100

101101 1. Create a web content filtering policy rule.

102102 1. Select the **SocialNetworking** web category.

103103 1. Enable **Source type** and select **Agent**.

104104 1. Set the policy action to **Block**.

105105

106 −This configuration blocks AI agent traffic to social networking sites while allowing non-agent traffic to access the same sites.

106 +This configuration blocks AI agent traffic to social networking sites while allowing user traffic to access the same sites.

107107

108108 ## Configure HTTP method request filtering (preview)

109109

⋯ 223 unchanged lines

Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 9 Oct 23:37 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.