Are you on a MDS platform?
If so, for 80.30 try here:
/var/opt/CPmds-R80.30/conf
You should have autoprovision.json there.
You could also try: "autoprov-cfg show all" from expert.
Here's a sample of what my script looks like:
(this part defines the controller(s)):
controllers:
Azure1:
class: Azure
credentials:
"client_id": "My_Azure_client_ID_here"
"client_secret": "More_privateclient_stuff_here"
"grant_type": "client_credentials"
tenant: My_Azure_tenant_ID
domain: "CMA_Mine-Mine-Mine"
subscription: "My_Azure_Sub_ID"
templates:
- Azure-DMZ
The controller calls the template, in this case Azure-DMZ. Here's the template (this will all show up in the same file) note we also enable the blades here:
Azure-DMZ:
anti-bot: true
anti-virus: true
identity-awareness: true
ips: true
one-time-password: "My-one-time-password-aka-SIC"
policy: "Azure_DMZ"
send-alerts-to-server: "CMA_Mine_Mine_Mine_Log_01"
send-logs-to-server: "CMA_Mine_Mine_Mine_Log_01"
version: "R80.20"
In my case, I have an MDS and a MLM, so I define that I want the logs to go to the MLM.
Note the policy line. That's the policy that will be assigned in the CMA to the autoprovisioned firewalls. Make sure this policy is created first. And make sure you have sufficient permits to continue talking to the firewall when that policy first starts so you don't lock yourself out.
When you go to push policy, you'll notice that you don't have to define the gateways like you normally would for a normal new setup.
