azure-mgmt-arizeaiobservabilityeval-dotnet
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 with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "azure-mgmt-arizeaiobservabilityeval-dotnet" from https://skillstore.io/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "azure-mgmt-arizeaiobservabilityeval-dotnet". Explain how to authenticate before listing organizations.
Expected outcome:
Use DefaultAzureCredential to create ArmClient, resolve the subscription, obtain the resource group, and enumerate its Arize AI organization collection.
Using "azure-mgmt-arizeaiobservabilityeval-dotnet". Plan a safe update for organization tags.
Expected outcome:
- Retrieve the named organization with an existence-aware method.
- Create a patch containing only the intended tags.
- Submit the update and handle Azure request failures.
Using "azure-mgmt-arizeaiobservabilityeval-dotnet". Describe direct access to one organization.
Expected outcome:
Create its resource identifier from the subscription, resource group, and organization name, then obtain the resource through ArmClient.
Security Audit
SafeAll 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.
Risk Factors
⚙️ External commands (40)
🌐 Network access (3)
🔑 Env variables (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). azure-mgmt-arizeaiobservabilityeval-dotnet security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet/audits/5BibTeX citation
@techreport{sickn33-sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet-2026,
author = {sickn33},
title = {azure-mgmt-arizeaiobservabilityeval-dotnet security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "azure-mgmt-arizeaiobservabilityeval-dotnet security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-azure-mgmt-arizeaiobservabilityeval-dotnet:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
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.
Try These Prompts
Show the package installation and authentication setup for an Azure .NET application. Use placeholders for every tenant, client, subscription, and secret value.
Draft a C# workflow to create an Arize AI organization in {resource_group}. Include marketplace, user, location, and long-running operation fields.Design C# methods to retrieve, list, update, and conditionally delete {organization_name}. Include not-found handling and cancellation support.Design an idempotent Azure service for Arize AI organizations. Cover direct identifiers, retries, polling, structured errors, least privilege, validation, and deletion confirmation.
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.
Avoid
- 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.