,
ensure that the Azure region you are deploying supports zones.
If the region does not, you can use an
Availability
Set
.
Enter a numerical value for the Zone parameter for each ION.
This is typically a numeric value and is a number in the range
of 1-3. When you use the same zone number for both vIONs, the
vIONs are deployed in the same zone, and there will be no use of
an Availability Set.
Specify
None
as the zone value, if there
is no Zone support in the region you're deploying or you wish to
use an availability set. The vIONs thereby will be deployed in
an Availability Set (across different fault or update domains)
within the same region.
Configure the vION
License and Secret Keys
obtained from
Prisma SD-WAN
Controller.
Configure the vION version. It's recommended to use the default
configuration.
Confirm if all resources are fully deployed and appear in the resource group
created.
If the zones configured are correct and are supported in Azure, the vIONs will
be deployed according to the specified availability zones. You can view and
access the vIONs in the
Prisma SD-WAN
portal.
It can take a while for the resources to be fully
deployed and the vIONs to connect to the controller.
Mark the availability zone as
None
, to create the
following resource within the resource group.
If Availability zones are not configured, verify the vIONs deployed across
different fault domains by accessing the vION instance overview page in the
Azure portal.
You must deploy both vIONs in the same resource
group along with one virtual network containing six subnets; three each for
each vION’s controller, internet, and LAN interfaces. You can now claim and configure the IONs in the Prisma
SASE portal.