This script collects information from provided Azure account and generates csv files for import into StratoZone for analysis. Generated files will be placed in ./output directory and a compress zip file will be created that can be imported directly to StratoZone using the import procedure.
NOTE: Script will collect data only on the instances user executing the script has access to.
-
Step 1: Login to Azure Console (https://portal.azure.com)
-
Step 3: Clone Script repo
git clone https://github.com/GoogleCloudPlatform/azure-to-stratozone-export.git
- Step 4: Access cloned project directory
cd azure-to-stratozone-export
- Step 5: Run script to start collection
./azure-export.ps1
- Step 6: Verify output file has been generated
ls ./azure-import-files.zip
-
Step 7: When the script completes, click on Upload/Download files icon.
-
Step 8: Enter the path to the output file.
/azure-to-stratozone-export/azure-import-files.zip
- Step 9: Click Download. File is ready for import into StratoZone portal.
- -no_perf - Default False. Use to indicate whether performance data will collected.
./azure-export -no_perf
- -threadLimit - Default 30. Use to set the maximum number of threads to start during performance data collection.
./azure-export -threadLimit 40
- -no_public_ip - Default False. Use to indicate whether public IP address will be collected.
./azure-export -no_public_ip
- -no_resources - Default False. Use to indicate whether deployed resources are collected.
./azure-export -no_resources
Azure Cloud Shell is the recommended environment to execute the collection script as it has all required components (PowerShell and Azure PowerShell module) already installed.
If the script will be executed from a workstation following components will need to be installed
- PowerShell 7.0.6 LTS, PowerShell 7.1.3, or higher
- Azure Az PowerShell module (https://docs.microsoft.com/en-us/powershell/azure/install-az-ps?view=azps-6.5.0)
The script needs read-only access to the Azure Subscriptions where collection will be performed.
If the execution of the script fails please contact [email protected] and attach log file located in ./output directory.