


This is required because not all powershell modules support alternate/modern way of authentication. User must have the following permissions -ī. Note: The cost of the Azure function application increases with the increase in SKU type.ĥ) Enter O365 domain you wish to scan and the credentials of User 1. Note: The cost of the Azure function application increases with higher plans. Minimum supported version: B2 (default value). The higher the plan, the faster the function application. The SKU plan for the function application. You can use the following command line parameters while running the script: This file contains the required code for the Azure functions that validate individual controls as well as the script to be executed (qualys_azure_installation.sh).Ģ) Unzip the file that you downloaded in a temp folder.Ĥ) Execute the qualys_azure_installation.sh script as - sh qualys_azure_installation.sh. User 2 with Global Administrator permissions and an active paid subscription of Microsoft Azure.įollow these steps to create a Office 365 Connector:Ģ) Create Connector in SaaSDR with Office 365 as application Create Azure Resourcesġ) Download the qualys_azure_setup.zip file by clicking here. User 1 with Global Reader and Privileged Role Administrator permissions. This is used to execute the script to complete the install.ģ) An active paid subscription of Microsoft Azure to create a serverless deployment containing the following resources-Īll these resources would be created in a separate Azure resource group for easy management.Ĥ) On your local computer, you must temporarily disable proxy while executing the scripts.ĥ) You must have the following two users: Please make sure you have the Azure CLI v 2.45.0 installed.Ģ) For Windows, ensure you have a bash terminal installed, for example Cygwin. Prerequisitesġ) The instructions involve running a script that uses the Azure CLI. To accomplish this, you also need to install the PowerShell Module (PM) in your Azure environment as mentioned in Step 4. Several of these controls can only be validated using PowerShell commands executed in your Azure environment. The Center for Internet Security (CIS) has published CIS benchmarks for O365 that can be validated using SaaSDR. For Office 365, you can validate your environment against CIS controls using SaaSDR. SaaS Detection and Response (SaaSDR) enables you to understand the compliance posture of your SaaS applications.
