How Activate License Counts Are Calculated

this article explains how activate measures managed identities for licensing purposes for information about the different identity license types, see activate identity license types activate licensing is based on the number of managed identities within the agreed scope of the purchased activate solution subscription a managed identity is an identity that activate is configured and available to manage an identity does not need to sign in to activate or have an action performed against it during a particular month in order to count towards licensing if the identity is within the agreed scope of activate and is available for activate to manage, it forms part of the licensed population what does activate measure? activate automatically records the number of managed identities within each applicable identity license type the standard activate identity license types are workforce identity custom or external identity managed only identity non human identity (machine, service and ai) each managed identity is assigned to one identity license type at a time the same human identity is not counted multiple times where activate manages multiple systems, applications or accounts associated with that person non human identities represent separate non human (machine) identities and are counted separately from their human owners how is the monthly license count determined? activate tracks managed identities throughout the month for licensing and reporting purposes, the monthly license count is the number of managed identities within each identity license type at the end of the month this includes terminated identities that remain within the managed population as part of the applicable termination or stand down process at month end this provides a consistent monthly measurement of the customer's licensed identity populations if an identity changes identity license type during the month, the type assigned to the identity at month end is used for that month's report for example, if a contractor classified as a custom or external identity becomes a permanent employee and is classified as a workforce identity before the end of the month, that identity will be reported as a workforce identity for that month what happens when someone leaves? when a managed identity is terminated, it may remain within the scope of activate for a defined termination or stand down period in accordance with the customer's configuration and business rules while the identity remains within this process, activate continues to treat it as a managed identity for licensing and reporting purposes, the monthly license count is based on the managed identity population at the end of the month a terminated identity is therefore included in the monthly license count if it remains within the managed population at month end once the termination process has been completed and the identity has been removed from the managed population, it will no longer be included in subsequent month end license counts for example, if an employee leaves on 15 august and remains within activate's termination process for 30 days, the identity will be included in the august month end license count once the 30 day period has been completed and the identity has been removed, it will not be included in the september month end license count what is the contracted license count? the contracted license count is the quantity of identity licenses the customer has committed to purchase for each applicable identity license type during the subscription term for an annual subscription, this quantity represents the customer's committed license level for the relevant 12 month subscription period for a monthly subscription, charges are based on the managed identity counts reported for that month monthly subscriptions monthly subscription customers are charged based on the managed identity counts reported for each month because the subscription charge reflects the licensed identity population reported for that month, an annual license review is not required this provides a pay as you go approach where monthly subscription charges reflect changes in the customer's managed identity populations annual subscriptions annual subscription customers have a committed contracted license count for each applicable identity license type for the duration of the subscription term normal changes in managed identity numbers during the year do not change the customer's annual subscription charge at renewal, activate reviews the managed identity counts reported during the preceding 12 months in order to determine whether additional licenses are required for the next subscription period how does the annual license review work? for each applicable identity license type, activate 1 takes the 12 monthly reported managed identity counts from the preceding subscription period 2 totals the 12 monthly counts 3 divides the total by 12 to calculate the average managed identity population 4 rounds the resulting quantity up to the nearest 10 identities 5 compares the result with the customer's existing contracted license count this provides a representative view of the customer's managed identity population over the preceding year where the annual review establishes that additional licenses are required, the contracted license count is increased for the next subscription period based on the annual review calculation any increase to the contracted license count takes effect from the beginning of the new subscription term annual license review example a customer has a contracted license count of 2,000 workforce identities over the preceding 12 months, their workforce identity population has varied as people have joined and left the organisation the total of the 12 monthly reported workforce identity counts is 25,200 the annual average is 25,200 ÷ 12 = 2,100 workforce identities the average is already a multiple of 10, so the reviewed license quantity is 2,100 workforce identities the customer's average managed identity population is therefore 2,100 compared with their current contracted license count of 2,000 as the annual review has established a higher license requirement, the customer's contracted license count for the next 12 month subscription period will increase to 2,100 workforce identities why does activate use a 12 month average? identity populations naturally change throughout the year organisations hire employees, contractors finish projects, seasonal workers come and go, business units change and access requirements evolve using the preceding 12 monthly license counts provides a more representative view of the customer's managed identity population than basing the next subscription period on the highest count during the year the lowest count during the year a single month's count the count on the subscription renewal date this approach allows normal changes in the customer's identity population to be reflected in the annual license review without allowing a temporary peak or low point to disproportionately affect the calculation how are different identity license types reviewed? where a customer uses more than one activate identity license type, each licensed population is measured and reviewed independently for example, a customer may have contracted license counts for 2,000 workforce identities 800 custom or external identities 400 managed only identities 150 non human identities activate reports each population separately and, for annual subscriptions, calculates the 12 month average for each applicable identity license type this allows the customer's subscription to reflect the different identity populations being managed rather than treating every identity as requiring the same type of license what about packages and add ons? identity license types and license counts determine the identity populations included within the customer's subscription the activate package purchased by the customer determines the capabilities available to manage those identities additional specialised capabilities may also be purchased as add ons some add ons have their own licensing rules and quantities based on the capability being provided where separate add on licensing applies, this will be identified in the customer's activate quote or subscription agreement in summary activate licensing is based on the managed identities that are within the agreed scope of the purchased activate solution subscription each managed identity is allocated one identity license type at any point in time monthly subscription customers pay based on the managed identity populations reported each month annual subscription customers commit to contracted license counts for the subscription term at renewal, activate uses the preceding 12 monthly counts to establish the average managed identity population for each identity license type where the annual review establishes that additional licenses are required, the contracted license count is increased for the next subscription period based on the annual review calculation packages determine the activate capabilities available to the customer, while add ons provide additional specialised capabilities where required together, this provides a consistent and transparent licensing approach that can adapt as an organisation's identity populations and requirements change over time