azure-communication-callingserver-java

Migrate legacy Azure CallingServer Java SDK integrations to Call Automation SDK.

2.9k|323|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/microsoft/skills --skill azure-communication-callingserver-java-microsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azure-communication-callingserver-java
Source: https://github.com/microsoft/skills/tree/main/.github/plugins/azure-sdk-java/skills/azure-communication-callingserver-java
Command: npx skills add https://github.com/microsoft/skills --skill azure-communication-callingserver-java-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams maintain legacy Azure Communication Services CallingServer Java SDK code and guides migration to the Call Automation SDK, reducing technical debt and ensuring continuity for existing projects.

Core Features & Use Cases

  • Migration guidance for legacy CallingServer Java projects to Call Automation.
  • Code mapping & comparisons showing old vs new API names, client builders, and updated dependencies.
  • Best practices for maintaining or phasing out deprecated code while adopting the latest Azure SDK.

Quick Start

Follow the migration guide to align deprecated CallingServer usage with the Call Automation SDK.

Frequently Asked Questions about azure-communication-callingserver-java

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

FAQPage Schema
How do I migrate legacy Azure Communication Services CallingServer Java SDK to Call Automation?

Migrate legacy CallingServer Java SDK to Call Automation by updating dependencies, replacing client builders, and applying API name mapping patterns provided in the migration guide. It covers client creation and replacement scenarios for transitioning deprecated code safely.

What is the best way to map old CallingServer Java API names to the new Call Automation SDK?

The best way to map CallingServer Java API names to Call Automation is using the provided code mapping comparisons, which detail old versus new API names, client builders, and updated dependencies for accurate migration.

Can I maintain deprecated CallingServer Java code while adopting the Call Automation SDK?

Yes, you can maintain deprecated CallingServer Java code while adopting Call Automation by following best practices for phasing out legacy code, reducing technical debt, and ensuring continuity for existing Azure Communication Services projects.

What dependencies do I need to update for Azure Communication Services Call Automation migration in Java?

Updating dependencies for Call Automation migration in Java involves replacing legacy CallingServer packages with the newer Azure SDK dependencies, aligning client builders and API calls to ensure continued support and functionality.

Does the Call Automation SDK support all legacy CallingServer Java integration scenarios?

The Call Automation SDK covers real-world migration scenarios for legacy CallingServer Java integrations, providing migration mappings and best practices, though some deprecated features may require replacement patterns to ensure safe transition.