Manage MongoDB Atlas Orgs in Azure

Azure.ResourceManager.MongoDBAtlas manages MongoDB Atlas Organizations as Azure ARM resources for unified billing through Azure Marketplace, via ArmClient with DefaultAzureCredential. It has a hard scope limit worth naming up front: it does NOT manage Atlas clusters, databases, collections, or users/roles - only the organization resource itself as an ARM/marketplace object; cluster-level work goes through the MongoDB Atlas API directly once the organization exists.

Creating an organization sets its location, marketplace subscription details (an Azure subscription ID plus offer details - publisher "mongodb", offer ID, plan ID/name, and billing term unit/ID), an admin user (email, UPN, name), and MongoDB-specific partner properties (the organization name), as a long-running operation. Organizations can be fetched from the collection by name or built as a resource identifier without an API call (a cheap way to get a handle before deciding whether to fetch data), listed at the resource-group or subscription level, tagged (add/replace-all/remove), updated via a patch object, and deleted (again long-running). Provisioning states span Succeeded, Failed, Canceled, Provisioning, Updating, Deleting, and Accepted; marketplace subscription status spans PendingFulfillmentStart, Subscribed, Suspended, and Unsubscribed.

Use it when provisioning or managing the MongoDB Atlas organization resource itself through Azure - marketplace subscription, admin user, tags, and lifecycle - as infrastructure-as-code integrated with Azure billing. Do not use it for anything inside the organization: clusters, databases, collections, and users/roles are managed via MongoDB's own Atlas API, not this SDK.

Input is organization configuration (marketplace offer details, admin user, partner properties) or a patch for updates. Output is the created/updated MongoDBAtlasOrganizationResource with its provisioning state, or a resource identifier for a lazy handle. Install it with:

dotnet add package Azure.ResourceManager.MongoDBAtlas
dotnet add package Azure.Identity
dotnet add package Azure.ResourceManager

Its own best practices: prefer async methods throughout, handle long-running operations either by blocking on WaitUntil.Completed or starting with WaitUntil.Started and polling UpdateStatusAsync() yourself, check ProvisioningState == Succeeded before treating an organization as ready, and build a resource identifier directly when you don't need to fetch data immediately. Common errors are named explicitly: ResourceNotFound (verify name/resource group), AuthorizationFailed (check RBAC on the resource group), InvalidParameter (a required property is missing), and MarketplaceError (a problem with the offer details or subscription itself).

It provisions against the Azure Marketplace mongodb/mongodb_atlas_azure_native_prod offer for unified billing, and hands off to the separate MongoDB Atlas API for everything inside the organization (clusters, databases, users).

.NET platform engineers provisioning MongoDB Atlas organizations on Azure Marketplace for unified billing - organization lifecycle, tagging, and marketplace subscription - as infrastructure automation, distinct from database administrators managing clusters through Atlas itself.