What are the steps required to make the software compliant, particularly for Articulate Storyline?
Also, could you provide the key points or a checklist/table of criteria that need to be considered to ensure compliance?
Currently, I can see only two entitlements, and Articulate AI Assistant is showing as compliant, while the others are not.
Could you please guide me on how to make the remaining components compliant?
Hi @akguj ,
I recently completed the compliance configuration for Articulate 360.
Below is a summary of the steps taken.
We had a Publisher Part Number (PPN) for Articulate 360, which was also available in the Content Library. An entitlement was created based on this PPN however, upon reviewing it, the entitlement had been created for Articulate 360 Teams, with Teams recognised as the edition.
On further analysis, I opened the Software Model and confirmed that all suite components were present under it.
During testing, I used the Show Matching Discovery Model option highlighted in the above image and noticed there were no matching discovery models returned. This is because our current discovery tool (SCCM) has not yet discovered edition-level data for Articulate 360.
To work around this, I removed the "Teams" edition from the search filter and re-ran the search at which point all Articulate-related discovery models appeared as expected.
I then checked whether a Software Model for Articulate 360 without an edition existed, and confirmed it did. If you don't have this in your environment, I would recommend creating one.
From there, I added downgrade rights at both the Software Model level (Articulate 360 Teams) and the Entitlement level, ran compliance, and everything processed as expected.
Note: All suite components - including Rise 360, Storyline 360, Replay 360, Peek 360, Review 360, Studio 360, etc. - will be covered under the Suite Components of the Software Model.
Additionally, Storyline (without the 360 suffix) has been identified as a Perpetual License product and will require a separate licence record to be created for it.
If this helped - amazing, you're welcome, go click Helpful and Accept as Solution. If it didn't - well, at least you learned what not to do. Either way, we grow.
Cheers, Abby
ITAM Principal Solution Architect
