Single service comparison

Azure groups data in containers and blobs, while Huawei OBS uses buckets and objects; the naming and access URL model differ, so applications embedding Azure-specific paths or the Azure Storage SDK won't target OBS without code or proxy changes. Azure exposes distinct block/append/page blob APIs, whereas OBS treats objects uniformly with optional POSIX-like operations such as append upload, rename, and modify. Both support S3-compatible REST, but Azure's first-class API is the Azure SDK and OAuth token auth, while OBS favors AK/SK signing and an S3-compatible interface, so SDK and auth integration must be reworked.

Durability and tiering models align in spirit but diverge in detail. Azure advertises 99.999999999% (11 nines) durability across LRS/GRS and pairs Hot/Cool/Archive with WORM and soft-delete/versions; OBS offers 12 nines (multi-AZ) durability, up to 99.995% availability SLA, and Standard/Infrequent Access/Archive classes with lifecycle rules. Archive retrieval differs: Azure uses rehydration to Hot/Cool; OBS supports both restored-direct-read and expedited 1–5 minute restore, with minimum storage durations (30 days IA, 90 days Archive) that must be mapped to Azure retention policies.

Integration and operational responsibilities differ. Azure natively couples with AD/Entra ID identity, Event Grid, Functions, and Data Lake Storage Gen2 (HNS) hierarchies; Huawei couples OBS with IAM, CDN, MRS, DLI, ModelArts, and DES for ingestion. For workloads needing a dedicated, isolated control plane or hardware tenancy, Huawei offers DOS (Dedicated OBS) as a separate deployment model rather than a tier of shared OBS, and Azure has no directly comparable dedicated-silo blob product, so the target selection depends on isolation, compliance, and capacity commitments rather than feature parity.

Start with an assessment that maps Azure blob types, redundancy (LRS/GRS/RA-GRS), tiers, encryption (CMK vs platform-managed), retention/WORM, and access patterns to OBS storage classes and bucket settings. Choose OBS Standard/Infrequent Access/Archive to mirror Hot/Cool/Archive; reserve Dedicated OBS (DOS) only when the workload requires dedicated capacity, isolation, or compliance commitments that shared OBS does not meet, since DOS is a different deployment model, not an interchangeable tier. Confirm regional availability and quotas for both before committing.

Move data using a Huawei-supported path: for large datasets use Data Express Service (DES) with import devices, and for online migration use OBS-compatible tooling that reads from and writes to OBS rather than assuming Azure SDK compatibility. Rewrite application code that uses the Azure Storage SDK or Azure REST and OAuth/Entra auth to use OBS AK/SK signature, the OBS SDK (10+ languages), or the S3-compatible interface; recreate lifecycle, versioning, soft-delete, replication, and immutable/WORM policies as OBS bucket configurations after validating each policy maps cleanly, since not every Azure policy has an exact OBS equivalent.

Validate before cutover: reconcile object counts, sizes, checksums (MD5/etag), and access control mappings between source blob ACLs/SAS tokens and OBS bucket policies/IAM; re-test read/write paths, retry semantics, multipart thresholds, and any CDN or function triggers that fire on object events, because eventing and notification wiring differ. Perform a read-only parallel run, then a controlled cutover with DNS or pointer swaps, and keep Azure read-only until reconciliation closes to avoid split-brain writes.

Account for cost and operational model changes. Azure typically bills capacity, transactions, retrieval, optional redundancy uplift, and egress; OBS bills capacity, requests, retrieval, and cross-region/interconnect transfer, while DOS carries a dedicated-capacity fee structure instead of pure pay-as-you-go. Re-run TCO using peak request volume, archive retrieval frequency, minimum-duration overwrites (30/90 days), and inter-region or Direct Connect egress, and confirm IAM roles, key management (KMS), and logging/audit replacements are in place since Entra ID and Azure Monitor have no one-to-one Huawei equivalent.