Arize AI Azure Management for .NET
Guides .NET developers through Azure-based management of Arize AI observability resources.
The document discloses authentication methods, environment variables, and the Azure/Marketplace data flow, and uses Azure SDK credential patterns. However, it does not specify least-privilege RBAC, secret handling, Marketplace PII protection, confirmation for external effects, or rollback; it also presents deletion without recovery guidance, so points are deducted.
Installation, authentication, CRUD, long-running operation, and 404 handling paths are reasonably consistent. However, package/API/type correctness is not reproduced in this file, and input validation, abnormal-input handling, diagnostic failures, and recovery from failed deletion are thin; the static calibration also limits the score.
The audience, .NET/Azure scenario, Arize trigger terms, and main CRUD use cases are clear. Non-fit boundaries, regional and permission prerequisites, Chinese-language support, and mainland-China reachability are not established, so adaptability is reduced.
The skill has clear sections for installation, package metadata, authentication, workflows, types, enums, practices, error handling, and links. It lacks a changelog, explicit maintenance owner/update path, known limitations, FAQ, permission notes, and fuller parameter constraints, so points are deducted.
It covers create, read, list, update, delete, and direct resource access, providing useful starting material. Marketplace IDs, subscription details, terms, and user data are placeholders or examples; there is no verified output or comparison with alternatives, so substantial adaptation remains necessary.
Specific package, API, dependency versions, and official links provide limited auditability. The supplied repository tests and CI do not demonstrate this skill's key paths, and the skill contains no third-party execution evidence or corroboration; only limited static evidence supports the score.
- Creating and deleting Azure Marketplace resources can cause external cloud-resource and billing effects; confirm the subscription, resource group, Marketplace terms, and deletion intent before execution, and maintain an independent recovery/audit process.
- The examples involve sensitive credential, email, and Marketplace user-data contexts; use secure secret storage, prevent log disclosure, and verify the actual RBAC scope.
- The supplied material does not reproduce the package version, API version, type names, or Marketplace parameters; compile against the target SDK and verify the official API documentation before use.
- No Chinese guidance or mainland-China reachability evidence is provided; access to Azure, NuGet, and external documentation should be confirmed separately.
What does this skill do, and when should you use it?
This skill helps .NET developers manage Arize AI Observability and Evaluation organizations through the Azure Resource Manager SDK. It covers Azure Marketplace-based creation, retrieval, listing, updates, deletion, and direct ARM resource access. The material includes NuGet installation, DefaultAzureCredential authentication, resource models, long-running operations, and error handling examples. It is a good fit for teams already using Azure subscriptions, resource groups, and .NET; it is not a general Arize SDK or machine-learning analytics guide.
Provides installation guidance for Azure.ResourceManager.ArizeAIObservabilityEval 1.0.0, Azure authentication environment variables, and asynchronous C# patterns for creating, retrieving, listing, updating, and deleting Arize AI organizations. The examples also cover Azure Marketplace subscription and offer details, user contact data, tags, resource identifiers, long-running operations, and handling 404 and Azure request failures.
- A .NET Azure developer needs to provision an Arize AI organization through Azure Marketplace and wants an ARM SDK example.
- A platform team needs to list or check Arize organizations across a resource group or subscription.
- An operations developer needs to update organization tags or delete an organization using the generated ARM resource types.
- An application team needs to authenticate to Azure from .NET with DefaultAzureCredential, managed identity, or a service principal.
What are this skill's strengths and limitations?
- Covers the organization resource CRUD lifecycle.
- Includes copyable asynchronous C# and Azure identity examples.
- States the API version, ARM type, dependency versions, and key model types.
- Includes long-running operations, conditional retrieval, direct resource access, and error handling.
- Scope is limited to Azure ARM management of Arize organizations, not Arize’s internal analytics features.
- Examples require an Azure subscription, resource group, and Marketplace offer information.
- The source provides no independent test coverage or verified platform matrix for this individual skill.
- The source does not document costs for Azure resource operations.
How do you install this skill?
Run npx skills add microsoft/skills and select this skill in the installer. The source file is .github/plugins/azure-sdk-dotnet/skills/azure-mgmt-arizeaiobservabilityeval-dotnet/SKILL.md; the README does not document the wizard’s exact single-skill selection flow. Install the SDK dependency with dotnet add package Azure.ResourceManager.ArizeAIObservabilityEval --version 1.0.0.
How do you use this skill?
In an Agent Skills-compatible coding agent, use a request such as: Create an Arize AI organization in .NET with Azure.ResourceManager.ArizeAIObservabilityEval and DefaultAzureCredential. Trigger terms include Arize AI, ML observability, ArizeAIObservabilityEval, and Arize organization. Configure an Azure subscription, resource group, and supported credentials before running the code.