Juniper Agile Licensing, transfers and audits describes how a Juniper licence moves through its lifecycle and which obligations the customer carries along the way. Juniper names six phases: purchase the entitlement, activate the licence, deploy the key, monitor, update, and renew subscriptions.[13] Most of the lifecycle runs through the Juniper Agile Licensing (JAL) portal. The portal activates and manages licences for Juniper hardware, software, and SaaS or cloud products, but it does not show Mist or Session Smart Router entitlements.[2] Contractually, the Juniper Purchase and License Agreement (JPLA) makes the customer responsible for tracking its use, truing up unpurchased use and keeping records for audit.[7] Licences are not transferable. Second-hand equipment is handled through the gray market reinstatement policy.[7][11]
Editions
This article covers processes rather than products. Perpetual licences are not portable except for RMA, while subscriptions are portable across like-device classes.[14] The licence types are defined in Juniper’s terminology:[1]
| Licence type | Key end date | Support | Move rules |
|---|---|---|---|
| Perpetual | None; valid for the life of the device or application | Bought separately | Cannot move after activation, except to an RMA replacement |
| Subscription | Yes; the term starts when Juniper fulfils the licence | Typically included (may come from a partner) | May move to another serial number; RMA transfer supported |
| Trial | Limited time; assisted trials normally 60 days | Not stated | Not applicable |
Metrics
The lifecycle uses these identifiers rather than metrics:
- Entitlement. The record of a software feature licence purchase. Juniper creates it when the licence SKU is fulfilled.[1][4]
- Activation. An activated entitlement, identified by the product instance where it is deployed. That is typically the serial number, the UUID of the compute, or the unique cloud application instance.[1]
- License key. An encrypted string that carries the SSRN, the start and end dates, the purchased features and scale, and the target serial number.[1]
- Software Support Reference Number (SSRN). A software serial number shown on the fulfilment document. Renewal quotes identify each subscription by its SSRN.[1]
The metrics themselves (device, class, vCPU, bandwidth and others) are covered in Juniper Networks licensing. The JPLA’s Network Element or Node definition applies to management software.[7]
Counting / floors
Delivery. A sales order may include several account IDs for customers and partners, and these account IDs control which licences are assigned and visible. Fulfilment sends an email to every address on the order. The email carries the licence name, a unique Activation Code, the SSRN and a Software Entitlement certificate.[4] A customer who does not receive the email can still see all entitlements linked to their user account in the JAL portal.[4] Some heritage products do not use JAL. They are delivered with an attached key, as a certificate only, or, in some legacy cases, as a paper document.[4]
Inventory. The JAL portal shows expiry dates and how many units of each entitlement are Used and Available. Entitlements that have already expired no longer appear. Full lists of entitlements and activations can be exported.[6] Because expired entitlements drop out of view, an export taken before expiry is the only record of them in the portal.
Revocation. An activation that is no longer needed can be revoked. A perpetual licence can be revoked only within 30 days of activation, while a subscription can be revoked at any time.[2] Catalog proof: Perpetual activations can be revoked only within 30 days.
RMA. The self-service RMA tool moves licences from the defective serial number to the replacement serial number. The replacement need not be the unit shipped on the RMA, and a spare from stock is acceptable, but it must be the same platform.[3] Catalog proof: RMA licence transfer requires the same platform.
Renewal. Every calendar quarter, Juniper creates renewal quotes for subscriptions alongside maintenance and support renewals. Each line identifies the original SSRN. After the renewal order is fulfilled, the new end date appears in the portal and a new key must be downloaded and installed.[1] Changing the term to co-term subscriptions is possible only at renewal. At any other time, a new term must be bought.[5] Catalog proof: Legacy to Flex migration and co-terming only at renewal.
Virtualization & partitioning
Licence keys for Juniper software products are not tied to the serial number of the product they are used on.[15] Activations for software identify the instance by the UUID of the compute or the cloud application instance.[1] For hardware, the JPLA lets operating system software included with the hardware run only on that hardware or its replacement.[7] Rules on moving licences between virtual hosts and clouds are in Juniper vSRX and cSRX licensing.
Cloud / BYOL
Cloud services follow separate lapse rules. Under the reinstatement policy, lapsed cloud subscriptions are backdated to the day after the expired term. After a 30-day lapse, access may be disabled or limited to read-only, or the right to use may be revoked. At that point a new subscription has to be bought.[10] Moving from an on-premise product to a cloud-hosted SaaS service counts as a new product purchase.[5]
Programs
Transfer and the gray market
The JPLA grants a “non-transferable” licence. Without written authorization, the customer may not sublicense, transfer or assign any right to the software, except where the law does not allow transfer to be restricted.[7] Neither party may assign the agreement without the other’s prior written consent.[7] Hardware transfers are subject to the inspection and reinstatement policies.[7] The November 2020 EULA went further. It barred transfer “including an Affiliate, even if You transfer title to the Juniper Platform”, and allowed title to a platform to pass only after the software had been deleted from it.[8] Catalog proof: Juniper software licences are not transferable.
The gray market policy (July 2025) covers new, used and refurbished products sourced outside Juniper’s authorized channels. Warranties extend only to the original purchaser, and support contracts do not pass to a new owner.[11] Software “is only licensed to the original purchaser”. The embedded Junos licence must be bought again through a Junos re-registration fee, and software sold separately from hardware must be bought new.[11] Reinstatement also requires a passed inspection and a fee equal to one year of Juniper Care Core Plus. Mist access points, Mist Edge and Session Smart Router hardware bought outside authorized channels are not reinstated at all.[11] Catalog proof: Gray market devices need a new software licence.
Support reinstatement
The inspection and reinstatement policy (May 2024) applies to original purchasers. After a lapse, a new support contract is backdated to the day after expiry, for up to 365 days. A lapse of more than 90 days adds a late fee of 3% of the net annual support price per device. A lapse of more than 365 days also requires a product inspection.[10] Support cannot be reinstated after a product’s Last Order Date.[10] The end-of-life policy defines Last Order Date as the last date for orders of the product and for new support contracts on it.[12] Catalog proof: Lapsed support is backdated up to 365 days with a 3% late fee.
Audits and compliance
JPLA (current). The customer must “track its Use of Software and True Up any unpurchased use”.[7] The Glossary defines True Up as the customer’s reconciliation of its deployment or use of unpurchased or unlicensed Juniper Solutions.[7] GTC s.12(g) requires accurate records for three years after the agreement ends. It also gives Juniper or its independent auditor reasonable access to information needed to verify compliance.[7] The clause sets no notice period, no frequency limit and no cost-shifting threshold. Catalog proof: JPLA audit: three-year records and access for Juniper or its auditor; Customers must track use and true up unlicensed use.
Scale on Demand (terms dated November 2023). These customers must deploy a Juniper licence tracking mechanism, such as Juniper Support Insights, J-Cloud or Mist, within 90 days. Juniper may audit quarterly, or more often if it has reasonable cause or tracking is not deployed. Required entitlements must be ordered within 30 days of the audit results. If actual use exceeds reported use by more than 5%, the customer pays Juniper’s reasonable audit costs.[9] Catalog proof: Scale on Demand: quarterly audit and 5% cost-shifting.
EULA (November 2020 Release). The licensee must keep software licence compliance logs, monitor use, and promptly buy rights for any excess.[8] Juniper may request log reports no more than once a year, and it or its auditors may access facilities, personnel, records and networks. A licensee found out of compliance pays the audit costs as well as the licence and maintenance fees needed to become compliant.[8] Catalog proof: EULA 2020: annual compliance log reports and audit costs.
Practical records. Juniper licences are soft-enforced by default. A device without a valid licence reports non-compliance through event notifications rather than blocking the feature.[1] For an effective license position, the usual records are therefore the JAL entitlement and activation exports, compared with what each device reports through its own licence usage command.[6] See software license audit and true-up.
Out of scope
- Partner and distributor program terms (Channel Schedule, Core Program Terms) and the Order Status Tool.
- Hardware warranty terms and support service descriptions.
- Mist subscription management, which happens in the Mist portal rather than JAL. See Juniper Mist AI subscriptions.