A common concern related to cloud-based services is the prevention of commingling of data that belongs to different customers. On Demand Audit has architected its solution to specifically prevent such data commingling by logically separating customer data stores.

Customer data are differentiated using a Customer Organization Identifier. The Customer Organization Identifier is a unique identifier obtained from Quest On Demand Core that is created when the customer signs up with the application.

This identifier is used throughout the solution to ensure strict data separation of customers' data. The technique used to separate custom data varies depending on the type service and storage.

• For Azure Data Explorer, each organization is contained within a separate database ensuring no mixture of data.
• For Azure Storage, a combination of techniques is employed. In Azure Blob Storage the primary technique employed is to keep each organization in a separate container. For other Azure Storage services and when Azure Blob Storage data cannot be separated using containers, the architecture will employ careful use of the organization identifier to ensure data is kept separate.
• For Power BI, each organization is contained within a separate workspace.
• For Azure Cosmos DB, the architecture will employ careful use of the organization identifier to ensure data is kept separate.