Modernize business units

We have modernized the Business Units security concepts in Dataverse. Users are no longer restricted to accessing/managing data in their own business unit. They can now access and own records across business units. Security roles from different business units can be assigned to the users regardless of the business unit the users belong to.

Announcement Blog Post -

[jamesdavidson]

Just found this today as we are planning to bring in business units! One step ahead which is great!

[CepaCode]

Truly a game changer! Sometimes you don't know how much you need a thing until you see it for the first time! Thanks!

[jean-philippecharlets]

Great to see this! We can make use of that new feature in CRM when the sales management of two business Units is merging but the sellers remain in their respective teams. 💡Easier to manage reorganizations without having to use the root BU.

[MrBencoussens]

This feature is just dragging, MS is falling behind on Enterprise Business Unit Access now, what's the deal?

[e-polk]

This was very helpful. I changed a user to a different business unit and updated her security role to Parent Child Business Units level on all my custom tables. She can no longer see the records on the Lookup tables that someone else entered in the Original Business Unit. Can you tell me what I might have done wrong?

[simonhetzel]

In recent years we've been encouraged to apply privileges via teams and NOT individual users (typically using AAD group-teams rather than owner-teams and using Team-member's privilege inheritance for privileges of basic/user scope). There need to be more details on how all this this relates to teams, teams with security roles, team-owned records, team-member's privilege inheritance and privileges of basic/user scope.

Does everything you've outlined apply equally to a team as well as a user? Can we move them between BUs in the new way just like users?