Microsoft Change Affecting Connex Studio Templates - February 2025

Problem:

Earlier this month we found a bug affecting Microsoft APIs that prevents Template creation or amendments in ConneX Studio, to fail

Attempts of these actions would result in a template status of "Failed Templating"

On investigation, we found that the root cause of this bug was a change deployed by Microsoft that results in the "ServerRelativePath" no longer being added to the workspace table in the SQL database. Unfortunately, Connex Studio expects this value as part of the validation that a Template has been successfully provisioned.   

We have created and tested a fix for this, which will be available in the March HotFix package available from March 15th for Atlas versions 5.4 and 6.0. 

This issue affects Connex Studio clients ONLY, and ONLY if the client tenant has received the Microsoft change, AND needs to create or amend any templates.

At ClearPeople we are working on the assumption that all clients will receive the Microsoft change in their tenants, but we cannot ascertain when this might happen as 365 tenants update at varying times and dates. To check if you are currently being impacted by this Microsoft change all you need to do is create a new template (it may be easier to provision a new workspace in order to test). If this templating fails (see screenshots below), you will need the hotfix prior to any future templating work.

See below a screenshot of Failed Template Provisioning in Connex Studio:

Recommendations:

If possible, until you have deployed the March HotFix in your tenant (after March 15th at the earliest), we'd urge you NOT to create NEW templates or amend EXISTING templates. 

If you absolutely MUST do either of these actions, please get in touch so we can work with you proactively on getting round this, rather than working reactively on Templates that are already broken. 

If you have any concerns or queries on the above, get in touch with the team at [e-mail]