4. Enables businesses achieve greater efficiency by sharing data and processes Shared application data across legal entities— party, location, products… Shared services across legal entities— procurement, centralized payments…

6. Managing shared data—requires centralized business processes Shared services—not managed centrally across all legal entities Separate AX instances—increased management overhead and TCO

8. Enable holding company subsidiaries to Share IT infrastructure across independent businesses Achieve strict data isolation across businessesReduce TCO for managing IT infrastructure

11. Metadata is common across partitions No partition specific customizations The same application code runs in all partitions License and configuration keys are shared across partitions Enabling or disabling a configuration key affects all partitions Named user licenses are calculated per principal, i.e. AD User, regardless of the number of partitions they have access to Default partition and company A default partition named “Initial” is always created for each AX instance The DAT company exists in every partition. It is automatically created when a new partition is created A company with the same name can exist in multiple partitions Partitions cannot be deleted Once created, they cannot be deleted. You cannot move LEs across partitions

12. AX users are defined per- partition Within a partition a principal can be associated with one AX user Each user has a “default” partition associated with them The principal that creates a new partition automatically becomes the Admin user in that partition AX user IDs other than Admin and Guest are unique across partitions Role definitions are shared across partitions User to role assignments are per-partition Organizations (e.g. departments, cost centers, etc.) and hierarchies are defined within a partition User-role-organization assignment is per-partition Users are only allowed to log into partitions that they have access to Intended partition is specified at session creation time via client configuration If no partition is specified then the user’s default partition is chosen

14. Per company tablePer partition tableShared table (System-only)

16. Shared application data Partition 1 (RecId = 123) Shared application data Partition 2 (RecId = 456) Shared application data Partition 3 (RecId = 789) GetCurrentPartitionRecId () = 123GetCurrentPartitionRecId () = 456GetCurrentPartitionRecId () = 789 curext() = company1curext() = company2 curext() = company3 curext() = company4curext() = company5curext() = company6

17. Shared application data Partition 1 (RecId = 123) Shared application data Partition 2 (RecId = 456) Shared application data Partition 3 (RecId = 789) select * from custtable where dataareaid = Company5 and Partition = 789

18. Batch framework Shared across partitions Batch jobs are associated with a partition Batch server executes jobs in the proper partition context Batch servers can process jobs for all partitions Application integration framework Managed centrally for all partitions Ports can be restricted to a single partition Partition context can also be provided for each inbound message Service definitions are shared across partitions Enterprise portal EP site shared across all partitions Default behavior is that the user’s default partition is chosen to log in to Query parameter in the URL can be used to log into a non-default partition Workflow Workflow metadata is shared across partitions Workflows are saved within a partition Workflow batch jobs and runtimes should be configured per partition BC.NET Partition is a parameter for logon Default partition for the user is chosen if non specified Client configuration for BC.NET has partition field similar to the interactive client

19. Source Version Upgrade all source companies into a single data partition on Dynamics AX 2012 R2 Upgrade source companies into multiple data partitions on Dynamics AX 2012 R2 Microsoft Dynamics AX 4.0 Microsoft Dynamics AX 2009 Microsoft Dynamics AX 2012 Microsoft Dynamics AX 2012 R1