Can the Azure Communication Services Calling SDK for Windows be redistributed inside a commercial desktop application?

Do not redistribute the Windows Calling SDK native DLLs in a commercial installer until Microsoft confirms that the exact package EULA grants redistribution rights and any necessary commercial video-codec rights.

Package and redistribution status

• The version found is 1.15.0-beta.1, not stable 1.15.0; it is explicitly a prerelease package.^1^
• The Calling SDK is closed-source and uses proprietary transport/interfaces.^2^
• Microsoft’s Windows Calling SDK release notes identify 2.0.0 as the latest supported baseline and say that it updates the licensing framework. This is the version to evaluate for a new commercial release.
• The available material does not establish an explicit right to bundle and redistribute the native runtime DLLs from either 1.15.0-beta.1 or 2.0.0. NuGet availability and Microsoft documentation showing how to install the package are not themselves redistribution grants.

Before shipping:

1. Download the exact 2.0.0 NuGet package.
2. Inspect its package metadata and all included LICENSE, EULA, notices, and third-party notices.
3. Look for an affirmative distribution clause covering the native binaries. A distributable-code list such as REDIST.TXT would be one possible form of authorization, but should not be assumed to exist.
4. Open an Azure support request and request written confirmation that the native DLLs from that exact version may be bundled in a commercial desktop installer.
5. Have counsel review the codec clause for your workflow, especially if the application records, transcodes, creates, or redistributes video.

Microsoft’s Windows documentation illustrates the distinction: a codec patent notice can permit ordinary internal business use while expressly excluding third-party redistribution and certain content-distribution scenarios.^3^ SDK binary redistribution and codec patent licensing are therefore two separate questions.

Customer-owned ACS resources

Having each customer supply its own ACS resource and tokens changes metering and operational ownership, not the license governing your redistribution of Microsoft binaries.

ACS/Teams interoperability usage is billed to the ACS resource used by the custom application, with no additional interoperability fee.^4^ It does not create or transfer a right for your company to copy Microsoft DLLs into your installer.

Microsoft 365 and Teams licensing

The answer depends on both the package version and identity model.

• For 1.15.0-beta.1: the repository’s EULA-BETA.txt states that use of the beta software requires a Microsoft Office 365 commercial subscription. That package-specific condition is separate from whether every external participant needs an individual Teams license. Confirm with Microsoft whose subscription satisfies the clause before using that beta commercially.
• External/BYOI users joining Teams meetings: the users of your custom application do not need Microsoft Entra identities or Teams licenses. They join as external users, while ACS usage is charged to the applicable ACS resource.^5^
• Teams-identity users: users authenticated as Teams users must have the appropriate Teams license.^4^
• Teams Phone operations: starting calls to Teams users and related Teams Phone scenarios require Teams Phone licensing and enterprise voice enablement; shared meeting-device identities can additionally require Teams Rooms licensing.^6^

For the described meeting-join scenario, the practical path is to move from the beta to 2.0.0, use BYOI for external participants if appropriate, and obtain written confirmation of commercial DLL redistribution and codec coverage under the exact 2.0.0 terms.

References

1. Azure.Communication.Calling.WindowsClient 1.15.0-beta.1
2. SDKs and REST APIs for Azure Communication Services - An Azure ...
3. MICROSOFT SOFTWARE LICENSE TERMS
4. Teams interoperability
5. Join a Teams meeting
6. Teams interoperability pricing