Symantec ZTNA License Binding Procedure

Terminology and Scope

• Site ID / Contract ID
  • Source: Purchase confirmation email (ESD)
  • Purpose: Used in the Broadcom Support Portal to associate entitlements and view contracts
• Environment
  • The operational tenant of Cloud SWG. Every subscription must be assigned to an Environment
• Enterprise Console
  • The console to configure bindings, and to view/manage subscription quantities and expiration dates
• Fulfillment Dashboard
  • Used to view and manage licenses, especially when subscriptions are placed in Tenant On Hold status

Step 0: Prerequisites

• ESD Email: Record Site ID and Contract ID

• Admin email address

Step 1: Create a Broadcom Support Portal Account

1. Open profile.broadcom.com/web/registration
2. Fill in details and verify your email
3. Once completed, you can access:
   • My Entitlements (contracts/licenses)
   • Download Center
   • Case Management (support cases)

Step 2: Associate Site ID in Support Portal

1. Log in to support.broadcom.com
2. Click your username → Request Site Access
3. Enter the Site ID → click Save
4. Wait for approval (up to 24 hours)
5. Verify that contracts appear under My Entitlements

Step 3: Create Environment and Bind Subscription

• Log in to Portal → Enterprise Console / Subscription Config
• Under Available Entitlements, locate ZTNA → click Configure / Manage

• Choose:
  • Assign to an existing environment
  • Or create a new environment → select No, create a new environment

• Fill in:
  • Environment Name (cannot be changed later)
  • Data Region
• Click Next

Click Submit after enter Tenant Name → wait for backend provisioning

Step 4: Verify Subscription

• Open the Environment → Cloud Secure Web Gateway
• Check:
  • Status: Active
  • Configuration Status: Completed
  • Quantity / Expiration Date: Matches contract
  • Instance: Login url

Step 5: Activation Email

1. After verification, the designated Admin email address will receive an Activation Email from Broadcom.
2. The email includes a unique activation link.
3. Click the activation link → you will be redirected to the Broadcom portal.
4. Complete the activation process.

Step 6: Handling On Hold Status

6.1 What is Tenant On Hold

• When the subscription cannot be directly assigned, the order will be On Hold

• Common reasons:
  • Tenant not specified
  • Add-On purchase requiring assignment to an existing tenant
  • Multiple tenants exist and selection is needed

6.2 Roles

• Only the Product Administrator (Ship-To contact on the contract) can resolve On Hold items in the Fulfillment Dashboard
• If you don’t have this role → apply in Support Portal → Request Site Access → Product Administrator

• Reference: KB206833

6.3 Fulfillment Dashboard Process

• Log in to support.broadcom.com
• Open My Entitlements – Fulfillment Dashboard (visible only to Product Administrators)
• Click Select Tenant

• Choose action:
  • Option A: Create New Tenant (Standalone products only)
  • Option B: Move to Existing Tenant (Add-On products must be assigned to an existing tenant)

Notes:

• If the order contains Standalone + Add-On products:
  1. Release the Standalone first → wait ~2 hours for tenant provisioning
  2. Return to Fulfillment Dashboard and release the Add-On into that tenant
• Reference: KB366761 – SaaS Tenant Hold and Release Process

Step 7: Add-On License Activation

1. Confirm the Add-On type (e.g., ZTNA Application Protection)
2. In the Fulfillment Dashboard, locate the On Hold Add-On entry
3. Select Move to Existing Tenant, and choose the target ZTNA Environment
4. Submit → Add-On will be activated on the tenant
5. Wait for backend synchronization (typically 1–2 hours)
6. Go back to Enterprise Console, binding Environment(same as ZTNA)

Step 8: Connectivity and Validation

1. Configure a ZTNA Site/Policy/Collector/Application
2. Try to connect to Application(RDP/Web/SSH)
3. Verify access logs under Logs tab

Verification Checklist

• Environment created and status is Active
• Environment shows correct Quantity / Expiration / Status
• Add-On License successfully assigned to the tenant
• Test that the Application can connect normally