Deep Security Manager 10 has reached end of support. Use the version selector (above) to see more recent versions of the Help Center.
Once you've installed Deep Security Manager, you can add and protect Microsoft Azure virtual machines by connecting a Microsoft Azure account to the Deep Security Manager. Virtual machines appear on the Computers page, where you can manage them like any other computer.
Topics in this article:
- Configure a proxy setting for the Azure account
- Add virtual machines from a Microsoft Azure account to Deep Security
- Manage Azure classic virtual machines with the Azure Resource Manager connector
- Remove an Azure account
- Synchronize an Azure account
- Go to Administration > System Settings > Proxies.
- In the Proxy Server Use section, select your proxy from the Deep Security Manager (Cloud Accounts - HTTP Protocol Only) list.
You can add virtual machines to the Deep Security Manager through the Computers page.
- On the Computers page, click Add > Add Azure Account.
Trend Micro recommends creating a dedicated Azure account for adding Azure resources into the Deep Security Manager. This allows you to change the user rights of the dedicated account independently of Azure accounts used to access and manage Azure resources.
- Enter your Azure portal account credentials and click Sign in.
The account must have been assigned the Global Administrator role for the Azure Active Directory and the Subscription Owner role for the Azure subscription. These privileges are required for Deep Security to automate the provisioning of a Service Principal object in the Azure Active Directory. Deep Security uses the Service Principal object to authenticate itself to your Azure subscription so that it can invoke the necessary Azure APIs to synchronize your Azure virtual machines in the Deep Security Manager console. For information on creating a user with a Global Administrator role, see Microsoft's Add or delete users using Azure Active Directory article.
- On the Deep Security Azure Connector permissions page, click Accept.
- Select the Azure Active Directory and Subscription Name, and then click Next.
- Review the summary information, and then click Finish.
The Azure virtual machines will appear in the Deep Security Manager under their own branch on the Computers page.
You can also manage virtual machines that were added with the Azure classic connector with the Azure Resource Manager connector, allowing you to manage both your Azure classic and Azure Resource Manager virtual machines with a single connector.
For more information, see Why should I upgrade to the new Azure Resource Manager connection functionality?
- On the Computers page, in the Computers tree, right-click the Azure classic portal and then click Properties.
- Click Enable Resource Manager connection.
- Select either the Quick method or the Advanced method, and then click Next. Follow the corresponding procedure above.
Removing an Azure account from the Deep Security Manager will permanently remove the account from the Deep Security database. This will not affect the Azure account. Virtual machines with Deep Security agents will continue to be protected, but will not receive security updates. If you later import these virtual machines from the same Azure account, the Deep Security agents will download the latest security updates at the next scheduled update.
- Go to the Computers page, right-click on the Microsoft Azure account in the navigation panel, and select Remove Cloud Account.
- Confirm that you want to remove the account.
- The account is removed from the Deep Security Manager.
When you synchronize (sync) an Azure account, Deep Security Manager connects to the Azure API to obtain and display the latest set of Azure VMs.
To force a sync immediately:
- In Deep Security Manager, click Computers.
- On the left, right-click your Azure account and select Synchronize Now.
There is also a background sync that occurs every 10 minutes, and this interval is not configurable. If you force a sync, the background sync is unaffected and continues to occur according to its original schedule.