Fix Teams Information Barrier Does Not Block a Chat in Teams Admin Center

When you create an information barrier policy in the Teams admin center, you expect it to block chats between two groups. But sometimes the policy does not block a chat, and users on opposite sides can still message each other. This happens because the barrier policy has not been applied to the users, or because the policy takes time to propagate. This article explains the root cause and gives you a step-by-step fix to make the barrier work.

You will learn how to verify the policy assignment, check the policy status, and force a refresh. You will also see what to do when the barrier still does not block a chat after a few hours.

Why Information Barriers Do Not Block a Chat in Teams

Information barriers in Teams are designed to prevent communication between two groups. When you create a barrier policy, you define segments and then create a policy that blocks communication between those segments. However, the policy does not take effect until it is applied to the users. The application process runs in the background and can take up to 24 hours.

The most common reason a barrier does not block a chat is that the policy is not assigned to the users. You might have created the policy but forgot to assign it to the user segments. Another reason is that the policy application has not run yet. The system applies barriers periodically, so a new policy may not be enforced immediately.

There is also a known issue where the policy status shows “Inactive” or “Pending” in the admin center. This means the policy has not been fully applied. You need to check the status and trigger a manual application if necessary.

How Information Barrier Policies Work

An information barrier policy consists of segments and rules. Segments are groups of users defined by attributes like department or location. The policy defines which segments cannot communicate with each other. When the policy is applied, Teams checks the segments of the sender and the recipient before allowing a chat. If the policy blocks the communication, the chat is prevented or the recipient is not searchable.

Steps to Diagnose and Fix the Information Barrier Policy

Follow these steps in order. The first step is to verify the policy assignment, then check the status, and finally force the application.

1. Open the information barrier policies page
   Go to the Teams admin center at admin.teams.microsoft.com. In the left navigation, select Information barriers under the Governance section. You will see a list of all barrier policies. Note the status of the policy that should block the chat. If the status is Active, the policy is applied. If it is Inactive or Pending, the policy is not fully applied.
2. Check the policy assignment for the specific user
   In the Teams admin center, go to Users > Manage users. Find the user who is sending the chat. Select the user, then in the flyout pane, go to Policy assignments. Look for the Information barrier row. It shows the policy name that is assigned to this user. If the policy is not listed, the user does not have the barrier policy. You need to assign it.
3. Assign the information barrier policy to the user
   If the policy is not assigned, select Edit next to the Information barrier row. Choose the correct policy from the dropdown and select Apply. Wait for the change to save. The assignment usually takes effect within a few minutes, but the barrier application may still take time.
4. Force the barrier policy application using PowerShell
   Open Windows PowerShell as an administrator. Connect to Microsoft Teams and Exchange Online using the Teams PowerShell module. Run the following command to start the barrier application: Start-InformationBarrierPoliciesApplication. This command triggers the policy application immediately. Wait for the command to finish. It may take a few minutes to complete.
5. Verify the policy status again
   After running the PowerShell command, go back to the Teams admin center and refresh the Information barriers page. Check if the status of the policy is now Active. If it is still Pending, wait for 30 minutes and check again. The application process can take up to an hour.
6. Test the chat between the two users
   Have the sender try to start a chat with the recipient. If the barrier is working, the recipient should not appear in the search results. If the recipient is visible, the barrier is still not applied. Repeat the PowerShell command and wait.

Using PowerShell to Check the Barrier Status

You can also use PowerShell to check the status of the barrier policy. Run Get-InformationBarrierPoliciesApplicationStatus to see the last application status. If the status is Completed, the policy has been applied. If it is Pending or Failed, you need to troubleshoot further.

If Teams Still Has Issues After the Main Fix

Users Can Still See Each Other in Search

If the barrier is active but users still see each other in search, the issue may be with the search index. Teams caches user profiles. Wait for 24 hours for the cache to refresh. You can also ask the user to sign out and sign back in to Teams to force a refresh.

The Policy Status Shows “Failed”

A failed status means the policy could not be applied. Check the segment definitions. Make sure the segments are correct and that the users belong to the right segments. Also verify that the policy rule is set to Block and not Allow.

The Barrier Only Works in One Direction

If the barrier blocks chats from group A to group B but not the reverse, the policy rule is not symmetric. Edit the policy and add a rule that blocks communication from group B to group A as well.

Teams Admin Center vs PowerShell for Barrier Management: Key Differences

Item	Teams Admin Center	PowerShell
Create policy	Yes, via GUI	Yes, via New-InformationBarrierPolicy
Assign to user	Yes, via user properties	Yes, via Set-InformationBarrierPolicy
Trigger application	No, automatic only	Yes, via Start-InformationBarrierPoliciesApplication
Check status	Shows Active or Pending	Shows detailed application status

The admin center is easier for simple checks, but PowerShell gives you more control and immediate action.

After following these steps, you can verify that the information barrier is blocking chats between the intended groups. Check the policy status regularly, especially after making changes. To avoid future delays, use PowerShell to trigger the application right after creating a new policy. This saves you from waiting for the automatic cycle.