# Manage MongoDB Atlas Organizations with Azure .NET

Azure Marketplace integration for MongoDB Atlas requires specific ARM models and workflows. This skill provides focused .NET guidance for provisioning and managing organization resources.

## Install

```bash
npx skillstore add sickn33/azure-mgmt-mongodbatlas-dotnet
```

## Metadata

- Status: approved
- Slug: sickn33-azure-mgmt-mongodbatlas-dotnet
- Skillstore revision: r2
- Version status: missing
- Tree hash: a14de18dd777be08dfc39176111d5338ddf73ae647a063f0c62e42ac8c951a97
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-mgmt-mongodbatlas-dotnet
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-azure-mgmt-mongodbatlas-dotnet
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-azure-mgmt-mongodbatlas-dotnet/manifest

## Capabilities

- Shows how to install the required Azure Resource Manager, MongoDB Atlas, and identity packages.
- Explains authentication with DefaultAzureCredential and ArmClient.
- Provides C\# workflows to create, retrieve, list, update, and delete MongoDB Atlas organization resources.
- Documents marketplace, offer, user, partner, provisioning, and subscription status models.
- Demonstrates resource group and subscription-level organization discovery.
- Explains asynchronous operations, status polling, resource identifiers, and common Azure errors.

## Use Cases

- Provision an Atlas organization: Create an Azure-managed Atlas organization with marketplace, administrator, partner, and tagging details.
- Standardize marketplace onboarding: Build repeatable organization provisioning and lifecycle workflows for Azure platform services.
- Troubleshoot ARM workflows: Inspect provisioning states, subscription status, resource identifiers, permissions, and common request failures.

## Prompt Templates

### Explain the SDK scope

```
Explain what Azure.ResourceManager.MongoDBAtlas manages. Compare its organization scope with Atlas cluster and database management.
```

### Plan organization creation

```
Plan a C# workflow to create an Atlas organization in {resource_group}. List required marketplace, user, partner, authentication, and validation inputs.
```

### Design inventory and tagging

```
Design an asynchronous C# workflow to list Atlas organizations across {subscription}. Update approved tags and report provisioning states without changing other properties.
```

### Review a production lifecycle

```
Review this Atlas organization lifecycle design: {design}. Identify permission, idempotency, polling, failure recovery, deletion, billing, and environment validation concerns.
```

## Limitations

- Covers MongoDB Atlas organizations exposed through Azure Resource Manager only.
- Does not manage Atlas clusters, databases, collections, users, or roles.
- Requires valid Azure credentials, permissions, subscription details, and marketplace offer information.
- Examples use placeholders and require validation against the target environment and current SDK version.

## Best Practices

- Use asynchronous SDK methods and handle long-running operations explicitly.
- Validate permissions, offer identifiers, billing details, and administrator data before provisioning.
- Use resource identifiers and provisioning states to confirm the intended resource before updates or deletion.

## Anti Patterns

- Do not use this SDK for Atlas clusters, databases, collections, users, or roles.
- Do not place real subscription identifiers or personal data in reusable prompts and examples.
- Do not delete or replace organization properties without explicit approval and current-state verification.

## Security Audit

- Audited at: 2026-07-23T21:32:38.873\+00:00
- Summary: All 73 static findings are false positives caused by Markdown backticks, fenced examples, and visible reference links. SKILL.md contains documentation only, with no executable scripts, automatic network requests, credential access, or prompt injection. No security remediation is required.

## Stats

- Views: 107
- Downloads: 10
- Favorites: 0
- Popularity score: 0