Add Tenants to Prisma Access

After you migrate the existing information as a first tenant, you can create and configure additional tenants. For each tenant you create after the first, Prisma Access creates a separate access domain with its own set of template stacks and templates and its own domain groups.
Use this workflow to add more tenants to Prisma Access.
If you are creating an all-new multi-tenant deployment, use this workflow to add the first tenant as well as additional tenants.
  1. Log in to Panorama as a superuser.
  2. Add and configure the tenant.
    1. Select
      Panorama
      Cloud Services
      Configuration
      , then
      Add
      a new tenant.
      Be sure that you select
      Remote Networks/Mobile Users
      ; to create and configure a Clean Pipe deployment, see Create and Configure Prisma Access for Clean Pipe.
    2. Specify a descriptive
      Name
      for the tenant.
    3. Add
      a new
      Access Domain
      , give it a descriptive
      Name
      , and click
      OK
      to return to the
      Tenants
      window.
      After you click
      OK
      , Prisma Access automatically creates templates, template stacks, and device groups and associates them to the access domain you create.
      multi-tenant-add-second-tenant-update.png
  3. Specify the amount of
    Bandwidth (Mbps)
    to allocate for the
    Remote Networks
    and the number of
    Users
    to allocate for the
    Mobile Users
    .
  4. Make sure that Prisma Access applied the template stack, template, and device group service settings to the service connection settings of the tenant you just created.
    1. Select the tenant you created from the
      Tenant
      drop-down.
      multi-tenant-select-tenant.png
    2. Select
      Panorama
      Cloud Services
      Configuration
      Service Setup
      .
    3. Click the gear icon to the right of the
      Settings
      area to edit the settings.
    4. Make sure that Prisma Access has associated the template stack (
      sc-stk-
      tenant
      ), template (
      sc-tpl-
      tenant
      ), and device group (
      sc-dg-
      tenant
      ) to your service connection settings.
    5. Make sure that the
      Parent Device Group
      is set to
      Shared
      and click
      OK
      .
      multi-tenant-service-settings.png
  5. Make sure that Prisma Access applied the template stack, template, and device group to the remote network settings.
    1. Select
      Panorama
      Cloud Services
      Configuration
      Remote Networks
      and click the gear icon to the right of the
      Settings
      area to edit the settings.
    2. Make sure that the Prisma Access has associated the template stack (
      rn-stk-
      tenant
      ), template (
      rn-tpl-
      tenant
      ), and device group (
      rn-dg-
      tenant
      ) to your remote network settings.
    3. Make sure that the
      Parent Device Group
      is set to
      Shared
      and click
      OK
      .
      multi-tenant-remote-network-settings.png
  6. Make sure that Prisma Access applied the template stack, template, and device group to the mobile user settings.
    1. Select
      Panorama
      Cloud Services
      Configuration
      Mobile Users
      and click the gear icon to the right of the
      Settings
      area to edit the settings.
    2. Make sure that the Prisma Access has associated the template stack (
      mu-stk-
      tenant
      ), template (
      mu-tpl-
      tenant
      ), and device group (
      mu-dg-
      tenant
      ) to your remote network settings.
    3. Make sure that the
      Parent Device Group
      is set to
      Shared
      and click
      OK
      .
      multi-tenant-mobile-user-settings.png
  7. Mobile User deployments only
    —Commit your changes locally to make them active in Panorama.
    A local commit is required for the mobile user changes to take effect.
    1. Select
      Commit
      Commit to Panorama
      .
    2. Make sure that the device groups, templates, and template stacks are part of the
      Commit Scope
      .
    3. Click
      OK
      to save your changes to the Push Scope.
    4. Commit
      your changes.
  8. Continue the configuration of your tenant.

Recommended For You