Loading
Looking for Recommended Practices for Tracking/Managing Monthly Cloud Subscriptions

We use several Atlassian products and add-ons, all billed monthly, with increases and decreases automatically added to our billing. (We have other monthly subscriptions as well, but this one seems to provide the most complicated set of requirements.)

 

I'd like to include all these user-based licenses in SAM so I have more complete information around monthly spend and forecasting annual spend. (6 of these are not yet known in DIS and I'm holding off on new requests while pondering how best to move forward)

 

I'm interested in hearing how others are attacking this challenge. At this time, I do the following:

 

  1. I have a single Atlassian agreement with an annual subscription.
  2. I have a license for each of the products/tools currently found as applications in SnowAtlas. (6)
  3. I update the cost and count in each license every month when our new invoice comes in. This is the path of least resistance, but I do then lose visibility to historical licensing and spending. Alternatively, I could copy licenses every month with a subscription range of one month, and archive the old ones. This seems cumbersome, particularly when I consider that between this specific example and my other monthly subscriptions, I would be doing this for dozens of licenses every month.

 

I imagine there are better ways to do this, and would love to learn and collaborate on finding something optimal!


  • Kristy Stroud (Flexera Software)

    Hi Silverian, this is a perfect use case for our SaaS Management solution within Snow Atlas as it was designed to ideally manage monthly subscriptions. Within SAM Core, I feel you are doing the optimal solution if your license count changes on a monthly basis. You mentioned this does not allow for tracking of the changes in license count so I would suggest adding this information to the notes section or as an attachment that could be updated.

    If the quantity you own remains the same but the usage changes, I would suggest using Custom Compare Values to update the license requirement and that would give you insight to the changes in the compliance position over the lifecycle of the license.

    Expand Post

Related  Product Forums


                     → Flexera One



                      → Snow Atlas



                      → FlexNet Manager



                      → Snow License Manager



                       → App Broker


       Need help finding an answer?


        Ask a Question →


Loading
Looking for Recommended Practices for Tracking/Managing Monthly Cloud Subscriptions