Skill

Manage Arize AI Resources on Azure

The .NET SDK for managing Arize AI Observability and Evaluation organizations on Azure via Resource Manager.

Works with azure

91
Spark score
out of 100
Updated yesterday
Version 15.7.0

Add to Favorites

Why it matters

Automate the provisioning and management of Arize AI Observability and Evaluation resources within your Azure environment using the .NET SDK.

Outcomes

What it gets done

01

Create, read, update, and delete Arize AI organizations.

02

Configure marketplace subscription details and user information.

03

Manage organization tags for environment and team categorization.

04

Integrate with Azure's resource management for seamless deployment.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-azure-mgmt-arizeaiobservabilityeval-dotnet | bash

Overview

Azure.ResourceManager.ArizeAIObservabilityEval

This skill covers the Azure.ResourceManager.ArizeAIObservabilityEval .NET SDK: creating, reading, listing, updating, and deleting Arize AI organization resources via ARM, with Marketplace and SSO configuration. Use it for provisioning-time management of Arize AI Observability and Evaluation organizations on Azure via ARM.

What it does

This skill covers Azure.ResourceManager.ArizeAIObservabilityEval, the .NET SDK for managing Arize AI Observability and Evaluation resources on Azure (v1.0.0 GA, API version 2024-10-01, ARM type ArizeAi.ObservabilityEval/organizations). Core workflows: creating an Arize AI organization via ArizeAIObservabilityEvalOrganizationData with a location, Marketplace subscription/offer details (publisher, offer, plan, and term IDs), a User contact block (first/last name, email), and tags, submitted as a long-running CreateOrUpdateAsync operation; retrieving an organization by name directly, by first checking ExistsAsync, or via GetIfExistsAsync to avoid exceptions on a missing resource; listing organizations scoped to a resource group or an entire subscription; updating an organization's tags via ArizeAIObservabilityEvalOrganizationPatch; deleting an organization; and accessing a resource directly by its ARM resource identifier without listing first. Key types include the OrganizationResource, its Collection, Data, Properties, MarketplaceDetails, OfferDetails, UserDetails, Patch model, and SingleSignOnPropertiesV2 for SSO configuration. Documented enums cover OfferProvisioningState (Succeeded/Failed/Canceled/Provisioning/Updating/Deleting/Accepted), MarketplaceSubscriptionStatus (PendingFulfillmentStart/Subscribed/Suspended/Unsubscribed), and SingleSignOnState/SingleSignOnType (Saml, OpenId).

When to use - and when NOT to

Use it for provisioning-time and management-plane operations on Arize AI Observability and Evaluation organizations in Azure via ARM - creating, reading, listing, updating tags on, or deleting an organization resource, or configuring its Marketplace subscription and SSO. Do not treat its output as a substitute for environment-specific validation or expert review.

Inputs and outputs

Given ARM identifiers (subscription, resource group, organization name) and typed data objects (ArizeAIObservabilityEvalOrganizationData, its Patch model), it produces ARM long-running operations returning an ArizeAIObservabilityEvalOrganizationResource, or throws Azure.RequestFailedException on failure - the documented pattern catches status 404 specifically for a missing organization before a generic handler reports the Azure error message.

Integrations

dotnet add package Azure.ResourceManager.ArizeAIObservabilityEval --version 1.0.0

Depends on Azure.Core >= 1.46.2 and Azure.ResourceManager >= 1.13.1, authenticates via DefaultAzureCredential, and reads AZURE_SUBSCRIPTION_ID, AZURE_TENANT_ID, AZURE_CLIENT_ID, and AZURE_CLIENT_SECRET as environment variables. The organization creation flow ties into Azure Marketplace directly - OfferDetails carries the publisher ID, offer ID, plan ID and name, and billing term unit/ID needed to attach an Arize AI Marketplace subscription to the new organization resource.

Who it's for

.NET developers provisioning and managing Arize AI Observability and Evaluation resources on Azure who want production patterns: async methods throughout, WaitUntil.Completed or manual polling for long-running operations, GetIfExistsAsync for conditional logic without exception-driven control flow, retry policies configured via ArmClientOptions, direct resource-identifier access to skip unnecessary listing calls, properly disposed clients via using statements, and using GetAllAsync at either resource-group or subscription scope depending on how broad the organization listing needs to be.

FAQ

Common questions

Discussion

Questions & comments ยท 0

Sign In Sign in to leave a comment.