Migrating from User Groups to Security Groups in Sparkrock 365 Before Version 25

Modified on Thu, 13 Feb at 6:06 PM

Overview

It is critical that this migration is completed before your system is upgraded to Version 25, as User Groups will be removed during the update.


As part of Microsoft Dynamics 365 Business Central’s 2024 Release Wave 2 (Version 25), Microsoft is deprecating User Groups in favor of Security Groups. This transition impacts Sparkrock 365 customers who currently use User Groups to manage permissions.


To ensure a seamless transition, Sparkrock has developed a migration tool to facilitate the migration from User Groups to Security Groups. 


This article outlines the required steps to prepare for and complete this migration.


Note: The Migration Tool outlined in the video is still in development. You will be notified by Sparkrock when it is available to use.




Key Takeaways

  1. Microsoft is replacing User Groups with Security Groups in Business Central Version 25.0. Therefore, action needs to be taken before Sparkrock 365 is updated to Version 25.
  2. Microsoft Administrators must create Security Groups in the Microsoft Admin Center or Azure Portal before the migration tool can be used.

  3. Sparkrock 365 Administrators must create Security Groups in Sparkrock 365 before the migration tool can be used.

  4. Migration must be completed before the upgrade to Version 25, as User Groups will no longer exist post-upgrade. Users with un-migrated User Groups may not be able to log in and perform their work.

  5. Only customers using User Groups with assigned Permission Sets are affected. If you assign permissions directly to users, no action is needed.


What Are Security Groups?


Security Groups offer the same ability to manage permission sets as User Groups, with the added advantage of working across all Microsoft 365 applications. This allows administrators to manage access across the entire Microsoft suite from a single location.


To ensure continued access and permission management, User Groups need to be migrated to Security Groups prior to the Version 25 upgrade.


Read about Security Groups in Sparkrock 365 Help.


Migration Process

Step 1: Creating Security Groups in Microsoft Admin Center or Azure Portal


Before running the migration tool, a Microsoft Administrator must create Security Groups in the Microsoft Admin Center for each existing User Group that needs to be migrated.


Export Existing User Groups and Members

  1. In Sparkrock 365, navigate to User Groups.

  2. Export the list to Excel.

  3. Export the members list separately.

  4. Share the exported data with Microsoft Administrators to create corresponding Security Groups.


Set up Security Groups in Microsoft Admin Center


These instructions are for the Microsoft Admin Center. If you use the Azure or Entra portal, the steps will be similar.


  1. Log in to Microsoft Admin Center.

  2. Navigate to Teams & Groups > Active teams & groups

  3. Create a new Security Group.

  4. Assign users to the Security Group based on existing User Group memberships.





Step 2: Set up Security Group in Sparkrock 365 and link it to the MS Entra Security Group

Once Security Groups are created on the Microsoft side, they need to be created in Sparkrock 365 and then linked to their corresponding Microsoft group.


Note: For the Sparkrock 365 migration tool to function optimally, the name of the new Security Group should match the name of the existing User Group.
  1. Create new Security Group

    • In Sparkrock 365, navigate to Security Groups.

    • Select + New


  2. Select the related MS Entra Security Group

    • Select the 3-dots button beside "Microsoft Entra security group"



    • Select the Security Group you'd like to create.

    • Select Create.



Step 3: Running the Sparkrock 365 Migration Tool

The Migration Tool is still in development. You will be notified by Sparkrock when it is available to run.

Once Security Groups have been created, use the Sparkrock 365 Migration Tool to transition from User Groups to Security Groups.

  1. Enable the Security Group Migration Feature:

    • In Sparkrock 365, search for Feature Management.

    • Locate Feature: Convert User Permissions.

    • Set the feature to Enabled for All Users.


    • Review the warning message and confirm your understanding.


  2. Execute the Migration Process:

    • The migration tool will attempt to match existing User Groups with newly created Security Groups.

    • If the system does not find an exact match, manually select the correct Security Group.

    • Review the assignments, make necessary changes, and finalize the migration.

  3. Post-Migration Actions:


    • User Group Permission Sets and Members will be migrated to the corresponding Security Groups.

    • Sparkrock 365 custom enhancements (Application Area Setups, Report Filtering, etc.) will be carried over.

    • User Groups will be permanently removed from Sparkrock 365.

    • Users should retain their previous permissions through Security Groups.


Action Items Recap

  • Microsoft Administrators  must create Security Groups in Microsoft Admin Center for each existing User Group.
  • Sparkrock 365 Administrators must create Security Groups in Sparkrock 365 and link them to the associated Entra security group.
  • When advised by Sparkrock: Run the Sparkrock 365 Migration Tool to transition User Groups to Security Groups.

  • Complete this process before upgrading to Version 25 to avoid losing permission assignments.

  • Read the release notes for further details on this change.

  • Contact Sparkrock Support or your Customer Success Manager if you need assistance.


Need Help?

If you need further guidance on this transition, contact Sparkrock 365 Support or consult your implementation consultant if you are in-project. Your Customer Success Manager can also provide additional support and consultation options.


Prepare ahead—ensure a smooth migration before the Version 25 upgrade!

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article