# Manage Arize AI Resources with Azure .NET

Managing Arize AI organizations through Azure Resource Manager requires precise SDK patterns. This skill provides focused .NET examples for authentication, lifecycle operations, listing, updates, and error handling.

## Install

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

## Metadata

- Status: approved
- Slug: sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet
- Skillstore revision: r2
- Version status: missing
- Tree hash: f665475a2b14ecb437b3f34d597d0cffea101e84737dbe7d6bdcc7ea0272703a
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-mgmt-arizeaiobservabilityeval-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, env\_access
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet/manifest

## Capabilities

- Shows how to install version 1.0.0 of the Azure Resource Manager package for Arize AI.
- Explains authentication with DefaultAzureCredential and ArmClient.
- Provides C\# patterns to create, retrieve, list, update, and delete Arize AI organizations.
- Demonstrates long-running operations, existence checks, retry guidance, and Azure error handling.
- Shows direct resource access through Azure resource identifiers.

## Use Cases

- Create an Arize AI Organization: Generate a C\# workflow that authenticates, selects a resource group, and creates an Arize AI organization.
- Automate Organization Maintenance: Build update, listing, existence-check, and deletion patterns for managed Arize AI resources.
- Add Reliable Resource Handling: Apply long-running operation handling, retries, direct resource identifiers, and RequestFailedException responses.

## Prompt Templates

### Set Up the SDK

```
Show the package installation and authentication setup for an Azure .NET application. Use placeholders for every tenant, client, subscription, and secret value.
```

### Create an Organization

```
Draft a C# workflow to create an Arize AI organization in {resource_group}. Include marketplace, user, location, and long-running operation fields.
```

### Manage an Existing Organization

```
Design C# methods to retrieve, list, update, and conditionally delete {organization_name}. Include not-found handling and cancellation support.
```

### Build a Reliable Lifecycle Service

```
Design an idempotent Azure service for Arize AI organizations. Cover direct identifiers, retries, polling, structured errors, least privilege, validation, and deletion confirmation.
```

## Limitations

- The skill provides guidance and examples; it does not execute deployments or verify results.
- Examples use placeholders and require valid Azure subscriptions, permissions, marketplace details, and resource names.
- The documented package is version 1.0.0 with API version 2024-10-01.
- The skill does not validate costs, organizational policies, marketplace eligibility, or production security controls.

## Best Practices

- Use DefaultAzureCredential with least-privilege Azure roles and avoid storing secrets in source code.
- Handle long-running operations, transient failures, cancellation, and RequestFailedException responses explicitly.
- Validate names, locations, marketplace fields, and deletion intent before submitting resource changes.

## Anti Patterns

- Do not replace placeholders with credentials inside prompts, generated files, logs, or source control.
- Do not delete organizations without an explicit confirmation step and a verified resource identifier.
- Do not assume sample marketplace values, API versions, or permissions match the target environment.

## Security Audit

- Audited at: 2026-07-23T21:13:25.057\+00:00
- Summary: All static findings are false positives caused by Markdown formatting, placeholder Azure credential names, documentation links, or ordinary SDK guidance. No executable Ruby backticks, credential collection, system reconnaissance, prompt injection, or malicious intent appears in SKILL.md.

## Stats

- Views: 98
- Downloads: 8
- Favorites: 0
- Popularity score: 0