azure-mgmt-weightsandbiases-dotnet
Manage Azure Weights & Biases with .NET
Provisioning W&B through Azure Marketplace requires precise SDK models, authentication, and lifecycle handling. This skill provides focused .NET guidance for deployment, SSO, updates, listing, and deletion.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "azure-mgmt-weightsandbiases-dotnet" from https://skillstore.io/skills/sickn33-azure-mgmt-weightsandbiases-dotnet.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-mgmt-weightsandbiases-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-weightsandbiases-dotnet". Create a deployment checklist for a W&B instance in East US with managed identity and Entra ID SSO.
Expected outcome:
Confirm subscription and Marketplace terms; gather administrator and SSO identifiers; create the instance; wait for Succeeded; validate identity, SSO, and tags.
Using "azure-mgmt-weightsandbiases-dotnet". Explain how to update tags without replacing the W&B instance.
Expected outcome:
Retrieve the existing resource, create a patch containing only the required tags, update the instance, and verify the returned resource details.
Using "azure-mgmt-weightsandbiases-dotnet". Review a proposed production deletion workflow.
Expected outcome:
Require explicit approval, verify subscription and resource identifiers, record dependencies, delete with completion waiting, and confirm the resource no longer exists.
Security Audit
SafeAll 55 static findings are false positives after contextual review of the only file, SKILL.md. The command alerts are Markdown formatting, the URLs are expected examples or references, and the reconnaissance alert is ordinary exception logging. No prompt injection, executable payload, secret collection, or unexplained network behavior appears; Azure changes remain explicit, credentialed examples.
Risk Factors
โ๏ธ External commands (49)
๐ Network access (5)
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-weightsandbiases-dotnet/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-azure-mgmt-weightsandbiases-dotnet?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-azure-mgmt-weightsandbiases-dotnet?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-mgmt-weightsandbiases-dotnet/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-azure-mgmt-weightsandbiases-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-weightsandbiases-dotnet security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-mgmt-weightsandbiases-dotnet/audits/5BibTeX citation
@techreport{sickn33-sickn33-azure-mgmt-weightsandbiases-dotnet-2026,
author = {sickn33},
title = {azure-mgmt-weightsandbiases-dotnet security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-azure-mgmt-weightsandbiases-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-weightsandbiases-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-weightsandbiases-dotnet/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-azure-mgmt-weightsandbiases-dotnet:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Bootstrap a .NET integration
Install the SDK, authenticate safely, and create a first W&B Marketplace instance with placeholder configuration.
Standardize MLOps provisioning
Build repeatable workflows for listing, tagging, monitoring, and managing W&B instances across Azure scopes.
Review enterprise access
Configure Entra ID SAML SSO, managed identity, regions, and lifecycle controls for an organizational deployment.
Try These Prompts
Show me how to install the preview .NET package and authenticate with DefaultAzureCredential. Explain required Azure permissions and placeholders.
Create a W&B instance in [region] within [resource group]. Include Marketplace details, managed identity, provisioning checks, and safe placeholder values.
Add Entra ID SAML SSO to [instance name] for [domains], then update governance tags. Preserve existing properties and explain validation steps.
Design a production workflow for listing, updating, monitoring, and deleting W&B instances. Include error handling, approval gates, rollback considerations, and least privilege.
Best Practices
- Use DefaultAzureCredential, managed identity, and least-privilege Azure roles.
- Replace every placeholder and validate the Marketplace plan, region, subdomain, and SSO identifiers before deployment.
- Wait for successful provisioning and handle RequestFailedException responses by status.
Avoid
- Do not place real tenant identifiers, API keys, administrator emails, or subscription details in shared source.
- Do not create, update, or delete production resources before confirming the subscription, resource group, instance name, and approval.
- Do not assume preview types, supported regions, or Marketplace values remain stable without checking current documentation.