# Manage Azure Bot Service with .NET

Managing Azure Bot resources with the .NET ARM SDK requires precise resource, channel, and authentication patterns. This skill provides focused examples for common management workflows.

## Install

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

## Metadata

- Status: approved
- Slug: sickn33-azure-mgmt-botservice-dotnet
- Skillstore revision: r2
- Version status: missing
- Tree hash: 211a2425d90dc54d80f02c2614215ad1c8349a50a328902f64ae0524c293eda6
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-mgmt-botservice-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: 69
- Public page: https://skillstore.pages.dev/skills/sickn33-azure-mgmt-botservice-dotnet
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-azure-mgmt-botservice-dotnet/manifest

## Capabilities

- Sets up Azure.ResourceManager.BotService and Azure.Identity packages for a .NET project.
- Authenticates ARM clients with DefaultAzureCredential and accesses subscriptions, resource groups, and bot collections.
- Creates and updates Azure Bot resources with endpoint, application, SKU, and location settings.
- Configures Direct Line, Microsoft Teams, and Web Chat channels through typed SDK models.
- Lists bot channels and reads bot metadata with asynchronous collection APIs.
- Demonstrates Direct Line key regeneration, bot deletion, and RequestFailedException handling.

## Use Cases

- Provision a bot: Create a typed .NET workflow for an Azure Bot resource with authentication, endpoint, SKU, and application settings.
- Configure bot channels: Add Direct Line, Microsoft Teams, or Web Chat configurations with the Azure management SDK.
- Review lifecycle operations: Assess update, key regeneration, deletion, error handling, and managed identity choices before production deployment.

## Prompt Templates

### Set up the SDK

```
Prepare a .NET project for Azure Bot Service management. Explain package installation, DefaultAzureCredential setup, required identifiers, and minimum Azure permissions.
```

### Create an Azure bot

```
Generate a C# workflow to create Azure Bot [name] in resource group [group]. Use region [region], endpoint [endpoint], and SKU [sku].
```

### Configure production channels

```
Design an idempotent workflow for [channels] on bot [name]. Include secure site settings, asynchronous operations, validation, and RequestFailedException handling.
```

### Review a lifecycle plan

```
Review this Azure Bot management plan: [plan]. Identify permission boundaries, failure handling, confirmation points for key regeneration or deletion, and production validation steps.
```

## Limitations

- Provides guidance and examples; it does not execute Azure operations or verify deployed resources.
- Requires an Azure subscription, suitable permissions, and an existing application identity.
- Does not cover bot conversation logic, message handling, or Bot Framework application development.
- Uses example names, endpoints, regions, and identifiers that require environment-specific replacement.

## Best Practices

- Prefer managed identity and DefaultAzureCredential, with least-privilege Azure roles for each environment.
- Use asynchronous SDK operations, wait for completion, and handle RequestFailedException by status and error code.
- Confirm resource identifiers and recovery plans before key regeneration, updates, or deletion.

## Anti Patterns

- Do not place real application secrets, channel keys, or tenant credentials in prompts or source code.
- Do not reuse example endpoints, names, regions, or identifiers without environment validation.
- Do not run destructive lifecycle operations without dependency checks and explicit user confirmation.

## Security Audit

- Audited at: 2026-07-23T21:17:23.222\+00:00
- Summary: All 70 static matches are false positives. They are Markdown code markers, placeholder Azure settings, example URLs, or official links, with no embedded execution or secret exfiltration. A medium-risk concern remains because the guidance includes key regeneration and bot deletion without a workflow-specific confirmation step.

## Stats

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