Provisioned

—You have added the egress IP addresses to your organization’s allow lists, have confirmed them as having been added in the Prisma Access UI by checking

Added to My Allow List

, and have committed and pushed your changes to make them fully provisioned.

Not Provisioned

—Prisma Access has allocated IP addresses for the location, and you have added the egress IP addresses to your organization’s allow lists and confirmed them as having been added in the Prisma Access UI, but you have not yet onboarded this location.

Cannot Be Provisioned

—You have onboarded this location, but have not yet checked

Add to My Allow List

and committed and pushed your changes.

Until you specify in Prisma Access that you have added these egress IPs to your organization’s allow lists and

Commit and Push

your changes, Prisma Access will not provision these IP addresses to your deployment.

Provisioned without enough capacity

—You have added the first set of egress IP addresses, have confirmed them as having been added in the Prisma Access UI, and have Committed and Pushed your changes. However, Prisma Access has added another set of IP addresses as part of an autoscale event, and those IP addresses have not been specified as added to your allow lists in the Prisma Access UI.

The following screenshot shows an example of a deployment that would be marked as

Provisioned without enough capacity

. Two IP addresses have been marked as

Added to My Allow List

; however, Prisma Access has added two more IP addresses to this location, and those locations have not been added in the UI.

Allowed

—You have added all IP addresses to the allow lists. If a large number of mobile users log in to a single location and trigger an autoscale event, Prisma Access will use the allow listed IP addresses for the autoscale event.

Not Allowed

—You have not specified all IP addresses as being added to your allow lists in the Prisma Access UI, or you have not committed and pushed your changes after marking them as added. If Prisma Access triggers an autoscale event, Prisma Access will not provision more IP addresses to add more capacity for the location.

Every time that you add a location, or every time that Prisma Access adds IP addresses as a result of an autoscale event, you need to refresh the page that contains the

Egress IP Allow List

table, specify

Added to My Allow List

to mark the IP addresses as being added to your organization’s allow lists, and

Commit and Push

your changes.