Service Provider Register
Which providers support CloudMonitor, what they process, and which data-location boundary applies.
Service Provider Register
Last reviewed August 24, 2026.
1. How to read this register
Data-Driven AI Pty Ltd uses the providers below to operate CloudMonitor and cloudmonitor.ai.
This register separates providers that may process customer application data from providers used for the public website and business relationship. During onboarding, each customer chooses an available Azure and Microsoft Fabric region, and CloudMonitor deploys a dedicated processing environment for that customer in the chosen region. That location does not automatically apply to identity, Marketplace, website, support, or provider operational records.
The term service provider is descriptive. A provider’s legal role can be processor, subprocessor, independent controller, or a combination of roles according to the activity and applicable law. The applicable customer agreement and provider contract determine the legal classification for a particular deployment.
2. Providers that may process customer application data
| Provider and service | Purpose | Data that may be processed | Location boundary |
|---|---|---|---|
| Microsoft Azure and Microsoft Fabric | Host CloudMonitor’s management plane and each dedicated customer processing environment CloudMonitor operates; provide OneLake access, storage, compute, reporting, monitoring, and supporting platform services | Entra and tenant identifiers, service configuration, Azure FOCUS cost and resource metadata, Fabric capacity metrics, connected AI-usage metrics, audit history, and derived reports | The customer chooses an available Azure and Microsoft Fabric region, and CloudMonitor deploys a dedicated processing environment for that customer in the chosen region. In the customer’s own Fabric tenant, which is the default arrangement, the modeled cost tables, the semantic model, and the CloudMonitor app run on Fabric capacity the customer owns, in the region the customer sets for that capacity. Under CloudMonitor-hosted, they run on CloudMonitor’s own Fabric capacity in the chosen processing region. The raw FOCUS export remains in customer-owned Azure Storage. The central CloudMonitor management plane operates in Australia East. Microsoft support and platform operations remain subject to Microsoft’s terms. |
| Microsoft Entra ID | Authenticate interactive users, apply the customer’s identity policies, support administrator consent, and return the limited delegated profile used by CloudMonitor | User principal name, object ID, display name, work email, tenant ID, sign-in, consent, and security metadata | Governed by the customer’s Microsoft tenant configuration and Microsoft’s identity-service terms. Entra processing is not represented as confined to the selected Fabric region. |
| Microsoft Azure OpenAI | Generate Finn answers when an authorized user submits a question | The submitted question, relevant customer cost data retrieved for the answer, visible conversation context, generated response, and content-safety or abuse-monitoring signals | Governed by the configured Azure model deployment type and Microsoft terms. Some deployment types process within a selected geography, while global or data-zone options can have different processing boundaries. CloudMonitor does not represent that every provider-side operation is confined to the selected Fabric region. |
Microsoft is the provider for every entry above, but the services are separated because their data and location boundaries differ. See Microsoft’s Privacy Statement and Azure Direct Models privacy documentation.
CloudMonitor does not use its source-control service as a destination for customer application data, so source control is not listed as a customer-data provider.
3. Website, business, and support providers
These providers support the public website, acquisition, security, and support. They do not host the dedicated customer cost-processing environment.
| Provider and service | Purpose | Data that may be processed | Location boundary |
|---|---|---|---|
| Cloudflare | Website hosting through Workers, content delivery, DNS, security, rate limiting, D1 form storage, Email Routing notifications, Turnstile, and operational website insights | HTTP request and security data; IP address and request headers; consent and routing signals; calculator or other form fields, inputs, results, source page, and approximate country when submitted | Cloudflare’s global network and provider-controlled locations. Website and form records do not inherit a customer’s selected Fabric region. |
| Google Tag Manager, consent-gated Google Analytics 4, and a user-requested privacy-enhanced YouTube video | For Analytics: page, event, campaign, device, browser, referrer, approximate-location, and pseudonymous identifier data. For YouTube: IP address, request headers, requested video, and player interactions | Google-controlled locations, which may include the United States and other countries. Google Tag Manager and Analytics do not load until the visitor allows the combined Analytics and marketing category. The YouTube player is not created until the visitor chooses to load the video. | |
| Consent-gated Insight Tag for campaign measurement, aggregate professional audience reporting, website actions, and retargeting | URL, referrer, IP address, device and browser characteristics, timestamp, advertising identifiers, and configured action data | LinkedIn-controlled locations, which may include the United States and other countries. The Insight Tag does not load until the visitor allows the combined Analytics and marketing category. | |
| AnyChat LLC | User-requested website support chat | Current page URL, IP address and technical session data; messages, contact details, and content the user chooses to submit | AnyChat states that it stores customer content in the European Union, including Germany. Its business operations and transfers can involve the United States and other provider locations. The widget loads only after a visitor actively requests support. |
Provider privacy information:
4. Microsoft Marketplace and customer-controlled providers
Microsoft Marketplace operates the storefront, purchase, billing, and publisher reporting systems under Microsoft’s own relationship with the purchaser and publisher. Microsoft and Data-Driven AI act as separate controllers for their respective Marketplace purposes. Marketplace customer-contact information made available to us is used for the transaction or to respond to an inquiry. Microsoft is not listed above as our payment processor or as a subprocessor for the customer’s payment method because CloudMonitor does not receive card or bank details.
A customer may also authorize CloudMonitor to read from Microsoft, Azure, or another connected provider under the customer’s own account and contract. A company does not become a CloudMonitor-appointed service provider merely because the customer directs CloudMonitor to read data from that company. The Privacy Policy explains how we handle the information after CloudMonitor receives or processes it.
5. Raw exports, derived data, and residency
Azure Cost Management writes the raw FOCUS export to customer-owned Azure Storage. The raw export stays there. CloudMonitor accesses it through scoped permissions and a OneLake shortcut, then runs the ingest, cleansing, and modeling in CloudMonitor’s own Fabric tenancy. Where the finished data rests follows the customer’s arrangement: in the customer’s own Fabric tenant, which is the default, the modeled cost tables, the semantic model, and the CloudMonitor app sit in a Fabric workspace on capacity the customer owns; under CloudMonitor-hosted, they sit in the Fabric workspace CloudMonitor runs for that customer inside its own tenancy.
This distinction matters when reviewing residency: each customer’s cost processing runs in the Azure and Microsoft Fabric region they select during onboarding. CloudMonitor’s Australia East management plane and the identity, Marketplace, website, support, and provider records described above follow their own boundaries.
The CloudMonitor app is a Microsoft Fabric App item, and Fabric Apps are still in preview and not offered in every region. CloudMonitor confirms which regions are available with the customer at onboarding.
Architecture and data flow sets out where each layer runs in both arrangements.
6. Changes and customer questions
We update this register when a provider, service purpose, data category, or location boundary materially changes. Where an applicable customer agreement or law grants advance notice or an objection right for a new subprocessor, that requirement continues to apply.
For the provider list, transfer information, or contractual terms applicable to a specific deployment, contact support@cloudmonitor.ai.
See CloudMonitor on your own Azure data.
CloudMonitor runs on your own Azure tenant — your spend, recommendations, and anomalies. Pricing is a fixed annual license.
