MongoDB Atlas Azure ARM Manager
Helps .NET developers manage MongoDB Atlas organizations through Azure Marketplace and Azure ARM.
The document scopes the capability to Azure ARM organization resources and exposes authentication variables, including the client-secret risk; there is no evidence of covert exfiltration or malicious behavior. However, create, update, and delete cause external changes without user-confirmation guidance, least-privilege RBAC requirements, data-flow disclosure, sensitive-data handling, or rollback/recovery instructions, so points are deducted.
Installation dependencies, core types, lifecycle workflows, long-running operations, and common errors are documented, making the main path plausible from static inspection. There are no skill-specific tests or reproduced results, some SDK signatures, API-version details, and Marketplace parameters cannot be verified from the supplied files, and abnormal-input/failure diagnostics are limited; the static cap therefore applies and points are deducted.
The audience, use cases, and boundaries are reasonably clear, including the explicit exclusion of Atlas clusters, databases, collections, and users; create, read, list, update, and delete scenarios are covered. Trigger conditions, finer non-fit boundaries, Chinese-language support, and mainland-China network reachability are not addressed, so points are deducted.
The document is well organized across installation, authentication, types, workflows, models, states, errors, and best practices. It includes MIT licensing, author/version metadata, and official documentation links. It lacks a changelog, compatibility matrix, explicit maintenance/update path, FAQ, and systematic known-limitations section, so points are deducted.
Examples cover the main organization-resource lifecycle and provide directly adaptable C# patterns. However, they contain placeholders, fixed Marketplace offer parameters, and example email data, with no evidence of compilation or end-to-end success; deletion also lacks recovery guidance. The static effectiveness cap applies and points are deducted.
The skill names a package version and API version and links to NuGet, Microsoft Learn, API reference, and the Azure SDK repository, providing some auditability. The repository also shows generic CI and test infrastructure, but no supplied evidence demonstrates skill-specific key-path tests or third-party execution results; the static cap applies and points are deducted.
- Require explicit confirmation before create, update, or delete, and verify the subscription, resource group, organization name, and RBAC permissions.
- Do not place AZURE_CLIENT_SECRET, email addresses, or other personal data in source code, logs, or prompts; add secure-storage and redaction guidance.
- Validate the examples against the actual NuGet and API versions, especially Marketplace offer, term, and patch parameters.
- Deletion has no rollback or recovery guidance; check dependencies, preserve required exports, and explain irreversible consequences first.
- No Chinese-language guidance or mainland-China reachability evidence is supplied; users in that environment should verify access to Azure, NuGet, and documentation.
What does this skill do, and when should you use it?
This skill guides developers in using the Azure.ResourceManager.MongoDBAtlas SDK to manage MongoDB Atlas organizations as Azure ARM resources. It covers creating, retrieving, listing, updating, and deleting organization resources. It also documents Azure authentication, Marketplace subscription details, provisioning states, and common failures. It does not manage Atlas clusters, databases, collections, or users and roles directly.
Provides installation commands and C# examples for Azure.ResourceManager.MongoDBAtlas, Azure.Identity, and Azure.ResourceManager; shows DefaultAzureCredential and ArmClient authentication; creates and retrieves MongoDB Atlas organization ARM resources; lists organizations by resource group or subscription; updates tags and organization user properties; handles long-running create, update, and delete operations; checks provisioning and Marketplace subscription states; and explains ResourceNotFound, AuthorizationFailed, InvalidParameter, and MarketplaceError failures.
- A .NET developer needs to provision a MongoDB Atlas organization with Azure Marketplace billing.
- A cloud engineer needs to create, inspect, or delete an Atlas organization inside an Azure resource group.
- An operations team needs to list Atlas organizations across a resource group or subscription and inspect provisioning state.
- An application team needs to update organization administrator details or Azure resource tags.
- A team needs Azure-side organization provisioning while continuing to use the MongoDB Atlas API for clusters and databases.
What are this skill's strengths and limitations?
- Covers the organization resource lifecycle: create, retrieve, list, update, and delete.
- Includes copyable C#, authentication, Marketplace configuration, and long-running-operation examples.
- Clearly separates Azure-side organization management from MongoDB Atlas data-plane management.
- Uses the MIT license, and the README describes ongoing development and a test harness for repository skills.
- Does not directly manage Atlas clusters, databases, collections, users, or roles.
- Requires an Azure subscription, resource-group permissions, and valid Marketplace offer details.
- The source provides no independent test-coverage evidence for this specific skill.
- The source does not document runtime support beyond the .NET and Azure SDK examples.
How do you install this skill?
Run npx skills add microsoft/skills and select this skill in the installation wizard. Its source path is .github/plugins/azure-sdk-dotnet/skills/azure-mgmt-mongodbatlas-dotnet/SKILL.md; the README says skills are installed in the selected agent directory, such as .github/skills/ for GitHub Copilot. In the .NET project, run: dotnet add package Azure.ResourceManager.MongoDBAtlas, dotnet add package Azure.Identity, and dotnet add package Azure.ResourceManager.
How do you use this skill?
Give the coding agent a concrete request such as: “Create an Azure ARM MongoDB Atlas organization named my-atlas-org with Marketplace subscription details using Azure.ResourceManager.MongoDBAtlas.” Set AZURE_SUBSCRIPTION_ID and AZURE_RESOURCE_GROUP; for service-principal authentication, the source also lists AZURE_TENANT_ID, AZURE_CLIENT_ID, and AZURE_CLIENT_SECRET. The examples use DefaultAzureCredential, ArmClient, and asynchronous ARM operations.
How does this skill compare with similar options?
Compared with using the MongoDB Atlas API directly, this skill targets Azure ARM and Azure Marketplace integration for the Azure-side organization resource; cluster and database management remains the responsibility of the MongoDB Atlas API.