migrating-cosmosdb-bulk-executor

Migrate Cosmos DB bulk operations from BulkExecutor to Microsoft.Azure.Cosmos SDK.

19|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-cosmosdb-bulk-executor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrating-cosmosdb-bulk-executor
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-cosmosdb-bulk-executor
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill migrating-cosmosdb-bulk-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill aids in the migration from the deprecated Microsoft.Azure.CosmosDB.BulkExecutor library to the native bulk execution support within the Microsoft.Azure.Cosmos SDK, ensuring compatibility and improved performance.

Core Features & Use Cases

  • Migration Support: Transition legacy bulk operations from the BulkExecutor to the Cosmos SDK.
  • Compatibility: Ensures seamless operation without the need for separate libraries.
  • Use Case: For instance, a developer can use this Skill to migrate an existing .NET application from the BulkExecutor to the Cosmos SDK, improving scalability and maintaining up-to-date library usage.

Quick Start

Migrate Cosmos DB bulk operations from Microsoft.Azure.CosmosDB.BulkExecutor to Microsoft.Azure.Cosmos with the migrating-cosmosdb-bulk-executor Skill.

Frequently Asked Questions about migrating-cosmosdb-bulk-executor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from deprecated CosmosDB BulkExecutor to the native .NET SDK?

Migrate from deprecated CosmosDB BulkExecutor by transitioning bulk database operations from Microsoft.Azure.CosmosDB.BulkExecutor to the integrated Microsoft.Azure.Cosmos SDK. This ensures compatibility with the latest Cosmos SDK and eliminates the need for separate bulk operation libraries.

Why should I replace the BulkExecutor library with the Cosmos SDK for bulk operations?

Replace BulkExecutor with the Cosmos SDK to maintain up-to-date library usage and improve scalability. The deprecated BulkExecutor library requires a transition to native SDK bulk execution to ensure long-term compatibility and support for .NET applications.

Does the native Cosmos SDK bulk execution support .NET Core applications?

Yes, native Cosmos SDK bulk execution supports .NET Core applications. Migrating to the Microsoft.Azure.Cosmos SDK ensures seamless operation across supported .NET frameworks without requiring the deprecated BulkExecutor library.

What is the best way to transition legacy CosmosDB bulk operations to an integrated SDK?

The best way to transition legacy CosmosDB bulk operations is automating the migration from the deprecated BulkExecutor to the native Cosmos SDK. This approach eliminates separate library dependencies and ensures seamless operation with the latest SDK.

What limitations exist when keeping deprecated BulkExecutor instead of migrating to Cosmos SDK?

Keeping the deprecated BulkExecutor introduces limitations in compatibility and scalability. Migrating to the native Cosmos SDK for .NET resolves these constraints, ensuring your bulk operations remain supported and integrated within the current environment.

Can I migrate Cosmos DB bulk operations without separate libraries using this approach?

Yes, you can migrate Cosmos DB bulk operations without separate libraries by using the native Microsoft.Azure.Cosmos SDK. This transition from BulkExecutor provides integrated bulk execution support, ensuring seamless compatibility and removing external dependencies.