Block Deepseek App Usage with Microsoft Defender for Cloud Apps

In today’s digital workplace, controlling access to certain applications is crucial for maintaining security and productivity. If your organization needs to prevent users from accessing the Deepseek app—whether for compliance, security, or policy reasons—Microsoft Defender for Cloud Apps offers a robust way to block this app’s usage effectively. This step-by-step guide walks you through configuring app discovery, creating policies, and blocking Deepseek to ensure your organization’s environment remains secure and compliant. Before starting, ensure you have the necessary permissions and that Microsoft Defender for Cloud Apps is properly set up in your environment.

What You’ll Need

• Microsoft Defender for Cloud Apps license (included with Microsoft 365 E5 or as a standalone subscription)
• Global administrator or Security administrator permissions in Microsoft 365 / Azure AD
• Access to the Microsoft Defender for Cloud Apps portal
• Enabled app discovery and log collection from your network and cloud services
• Basic knowledge of policies and app discovery in Defender for Cloud Apps

Step-by-Step

1. Verify App Discovery is Enabled
   First, ensure that app discovery features are enabled and logs are being collected. Navigate to the Microsoft Defender for Cloud Apps portal, select Discover > App Discovery. Confirm that data collection is active and that your environment is generating sufficient logs for analysis.
2. Identify Deepseek App in the App Discovery Dashboard
   In the App Discovery dashboard, review the list of detected cloud apps. Use the search or filter options to locate Deepseek. Confirm its presence and note the associated user activity and traffic details for future reference.
3. Create a New App Discovery Policy (Optional for better control)
   To refine detection, you may create a policy to monitor Deepseek more closely or to ensure it appears in your reports. Navigate to Policies > Create Policy, choose App Discovery as the policy type, and set criteria to detect Deepseek specifically.
4. Create a Conditional Access App Control Policy to Block Deepseek
   In the Microsoft Defender for Cloud Apps portal, go to Control > Policies, then click Create Policy. Select Session Policy for real-time control.
   • Name your policy, e.g., “Block Deepseek App Usage”.
   • Select the users or groups this policy will target.
   • Under Cloud Apps or Actions, choose Include and select Deepseek from the list of discovered apps.
   • In the Session Control section, choose Block Access.

   Save your policy. This policy will now actively block user sessions to Deepseek.

5. Test the Policy
   After deployment, test the policy by attempting to access Deepseek from a targeted user account or device. Verify that access is blocked and that the policy logs indicate enforcement.
6. Monitor and Review Policy Effectiveness
   Regularly review the policy logs to ensure it’s functioning correctly. Adjust user groups or app selection as needed to refine control.

Common Mistakes

• Not enabling or properly configuring app discovery logs, leading to incomplete detection of Deepseek.
• Creating policies that target the wrong user groups or cloud apps, resulting in ineffective blocking.
• Failing to test policies after deployment, which can cause false assumptions about their effectiveness.
• Overlooking the need to update policies as apps evolve or new versions of Deepseek are released.
• Ignoring the importance of proper permissions; ensure you have the necessary admin rights to create and enforce policies.

Tips

• Use the app discovery dashboard regularly to stay updated on newly detected cloud apps like Deepseek.
• Combine session policies with alert policies for comprehensive monitoring and enforcement.
• Document your policies and procedures for audit purposes and future reference.
• Leverage user and device context in policies to create more granular access controls.
• Stay informed about updates to Deepseek and similar apps to adjust your policies proactively.

Troubleshooting

If your policy doesn’t seem to be blocking Deepseek as intended, consider the following steps:

• Verify Detection: Confirm that Deepseek is appearing in the app discovery dashboard and that logs are being collected properly.
• Check Policy Scope: Ensure the policy targets the correct users, groups, and cloud apps. Sometimes misconfigured filters cause the policy to miss the intended app.
• Review Policy Settings: Make sure the session control is set to Block Access and that the policy is enabled.
• Test with Different Accounts: Use multiple user accounts to verify if the policy applies universally or selectively.
• Consult Logs: Use the activity logs to see if attempts to access Deepseek are being intercepted and blocked. If not, adjust policies accordingly.
• Update App Discovery Data: Sometimes, new app versions or configurations aren’t immediately detected. Refresh or reconfigure discovery settings as needed.

If issues persist, consider reaching out to Microsoft support or consulting the latest documentation for Defender for Cloud Apps.

Frequently Asked Questions

1. Can I block Deepseek for all users at once?

Yes, by configuring your policy to target all users or specific groups, you can block Deepseek across your entire organization or selected segments.

2. Will blocking Deepseek disrupt other services?

Blocking Deepseek via Defender for Cloud Apps only affects access through cloud app sessions monitored by the platform. It should not impact other unrelated services or applications.

3. How often should I review my policies?

Regular reviews—monthly or quarterly—are recommended to ensure policies remain effective, especially as new apps and versions are released.

4. Is it possible to create exceptions for certain users?

Yes, you can configure policies with user or group exclusions to allow specific users access while blocking others.

5. Does blocking Deepseek affect on-premises access?

Blocking via Defender for Cloud Apps primarily controls cloud app sessions. On-premises access would require additional controls like network firewalls or endpoint policies.

6. How do I verify that the block is working?

Attempt to access Deepseek with a user targeted by the policy and confirm that access is denied. Check the activity logs for enforcement details.

Related

• How to Block Allow Paste Popup on iPhone in iOS 17
• How to Block All Websites Except One on Windows 10 and 11
• How to Block Adult Websites in Windows Using DNS Services