We’ve renamed Microsoft Cloud App Security. It’s now called Microsoft Defender for Cloud Apps. In the coming weeks, we’ll update the screenshots and instructions here and in related pages. For more information about the change, see this announcement. To learn more about the recent renaming of Microsoft security services, see the Microsoft Ignite Security blog.

If you work with both Defender for Cloud Apps and Zscaler, you can integrate the two products to enhance your security Cloud Discovery experience. Zscaler, as a standalone cloud proxy, monitors your organization’s traffic enabling you to set policies for blocking transactions. Together, Defender for Cloud Apps and Zscaler provide the following capabilities:

  • Seamless deployment of Cloud Discovery – Use Zscaler to proxy your traffic and send it to Defender for Cloud Apps. This eliminates the need for installation of log collectors on your network endpoints to enable Cloud Discovery.
  • Zscaler’s block capabilities are automatically applied on apps you set as unsanctioned in Defender for Cloud Apps.
  • Enhance your Zscaler portal with the Defender for Cloud Apps risk assessment for 200 leading cloud apps, which can be viewed directly in the Zscaler portal.


  • A valid license for Microsoft Defender for Cloud Apps, or a valid license for Azure Active Directory Premium P1
  • A valid license for Zscaler Cloud 5.6
  • An active Zscaler NSS subscription


  1. In the Zscaler portal, do the steps to complete the Zscaler partner integration with Microsoft Defender for Cloud Apps.
  2. In the Defender for Cloud Apps portal, do the following integration steps:
    1. Click on the settings cog and select Cloud Discovery Settings.
    2. Click on the Automatic log upload tab and then click Add data source.
    3. In the Add data source page, enter the following settings:
      • Name = NSS
      • Source = Zscaler QRadar LEEF
      • Receiver type = Syslog – UDP

      data source Zscaler.


      Make sure the name of the data source is NSS. For more information about setting up NSS feeds, see Adding Defender for Cloud Apps NSS Feeds.

    4. Click View sample of expected log file. Then click Download sample log to view a sample discovery log, and make sure it matches your logs.
  3. Investigate cloud apps discovered on your network. For more information and investigation steps, see Working with Cloud Discovery.
  4. Any app that you set as unsanctioned in Defender for Cloud Apps will be pinged by Zscaler every two hours, and then automatically blocked by Zscaler. For more information about unsanctioning apps, see Sanctioning/unsanctioning an app.

Source : Official Microsoft Brand
Editor by : BEST Antivirus KBS Team

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

(Visited 4 times, 1 visits today)