Azure

Azure customers can use enterprise cloud controls for identity, access, retention, encryption, and compliance.

Tenant and RBAC controls let organizations narrow who can reach cloud workloads before optional AI services are enabled.

Azure is an enterprise cloud context rather than a consumer ad-profile product.

Admins can govern where AI-capable services are turned on and what data they can reach.

AI and telemetry services can process workload data depending on customer configuration.

Diagnostics, logs, and connected Microsoft services mean workloads are not isolated to one simple product boundary.

Data can still flow through admins, support, subprocessors, integrations, diagnostics, and legal requirements.

Connected services and monitoring tools can broaden access beyond the most obvious workload boundary.

Microsoft enterprise cloud commitments separate customer content from broader consumer data contexts.

Admins can use RBAC, policies, and tenant boundaries to restrict internal access to cloud workloads.

Data residency, encryption, and region choices can limit who accesses some classes of data.

Customer-controlled integrations and service choices are not universally forced across every tenant.

Azure still processes service telemetry, diagnostics, billing, and security data.

The most important tracking-related choices live with tenant administrators rather than ordinary end users.

Customers can configure logs, diagnostics, regions, identity, and monitoring.

Azure is an infrastructure platform rather than a direct advertising destination.

Tenant governance can narrow some telemetry exposure by limiting what services are enabled.

Retention still varies by service, logs, backups, legal holds, and customer configuration.

Archived logs, backups, and connected services can preserve copies outside a single workload's main lifecycle.

Customers can configure retention, deletion, backup, and data residency across services.

Tenant governance and policy tooling let organizations define how long workloads and logs persist.

Enterprise cloud compliance features give customers more lifecycle control than consumer-grade services.

Deletion and residency controls help narrow where copies remain over time.

Admins can manage RBAC, policies, encryption, monitoring, retention, and data residency.

Tenant-wide governance gives organizations consistent access and compliance defaults.

Cloud architecture choices let teams isolate workloads, keys, and services more tightly than generic SaaS tools.

Deletion, retention, and export controls are customer-governed rather than opaque vendor-only processes.

Privacy still depends heavily on architecture and cloud governance.