How to fix Error 8523 "Missing mediaConfig information" when joining Teams meetings with Application-Hosted Media Bot using Graph Communications SDK v1.2.0.850?

Question

I am building an Application-Hosted Media Bot using Microsoft Graph Communications SDK v1.2.0.850 to join Microsoft Teams meetings. When calling Client.Calls().AddAsync() with properly constructed JoinMeetingParameters, Microsoft Graph returns error 8523 with the message “Missing mediaConfig information.”

All required configuration has been verified:

Public IP address is valid and reachable

Certificate is installed and valid in the Windows Certificate Store

Callback URL is accessible and returns HTTP 200

Required Azure AD permissions (e.g., Calls.JoinGroupCall.All) are granted

MediaPlatformSettings are fully populated and passed via builder.SetMediaPlatformSettings(), including:

Certificate thumbprint

Internal and public ports

Public IP address

Service FQDN

Application ID

Known issues have already been addressed:

Treating MessageId = "0" as null

Overriding public IP resolution

Correct tenant ID extraction from the meeting URL

Despite this, client.Calls().AddAsync() fails with error 8523, indicating mediaConfig is missing.

When I send a manually constructed raw HTTP POST request to the Graph API that explicitly includes mediaConfig, the request succeeds. This suggests the SDK may not be serializing or sending mediaConfig correctly.

---

Questions

Is SDK v1.2.0.850 failing to serialize or include mediaConfig in the request body?

What is the expected structure of mediaConfig in the Graph API join-call request? Is there a reference example of a valid payload?

Is this a known issue in SDK v1.2.0.850, and should I upgrade to a newer version?

How can I inspect or log the raw HTTP request generated by the SDK to confirm whether mediaConfig is being sent?

---

Environment

Microsoft.Graph.Communications.Calls: v1.2.0.850

Microsoft.Graph: v4.54.0

Microsoft.Skype.Bots.Media: v1.19.0.25-alpha

Platform: Windows Server (.NET Framework 4.8)

Hosting: Azure VM (self-hosted)

Answer 1

Hi @SarveshSwami,

Welcome to Microsoft Q&A and thank you very much for bringing this issue to our attention.

Your questions content was initially duplicated. We deleted the duplicated part to make this clearer.

Please note that as a Microsoft Q&A moderator, I do not have access to your application configuration, and my testing environment is limited. Therefore, I can only provide guidance based on available documentation and resources. That said, I will try to assist you as much as possible.

Based on your description and the troubleshooting you have already completed, it is very likely that Microsoft Graph Communications SDK v1.2.0.850 is not correctly serializing or including the mediaConfig object in the request body. This can occur because the SDK version you are using is outdated, and its request‑generation logic may no longer align with current Microsoft Graph service expectations.

At present, the recommended and supported version of the Graph Communications SDK is 1.2.0.15690, which contains significant updates and dependency alignments compared to v1.2.0.850. Upgrading to a newer version is strongly recommended when possible.

As I checked, you can verify the latest version of each Communications SDK component and review its release notes/changelog directly here.

Note: Microsoft is providing this information as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link.

When upgrading, please ensure that all dependency version requirements for the Communications SDK are followed.

To verify what the SDK is sending, you can use the Communications SDK built‑in logging capability, which can emit HTTP trace events. By subscribing an IObserver<LogEvent> to the GraphLogger, you can inspect the outgoing POST request and confirm whether mediaConfig is included in the payload.

For more information on enabling SDK logging, you can check this Microsoft documentation here.

Regarding whether this is a known issue, from my research, currently, there are no officially documented known issues specifically calling out this behavior in SDK v1.2.0.850. However, because this SDK version is no longer current, it is not guaranteed to behave correctly with today’s Graph service contracts. For this reason, upgrading remains the recommended remediation path.

For the expected mediaConfig structure in Graph API call or meeting join requests, you can review the official examples provided in this Microsoft Graph documentation.

This summary is based on my findings from the community and several relevant threads. However, it may not accurately reflect the behavior in question. To help you reach your goal more effectively, I recommend posting a thread on the Microsoft Tech Community forum. It’s a great platform for deeper technical discussions and connecting with individuals who have hands-on experience and expertise. They’re best positioned to provide guidance and valuable insights on this topic.

I hope this helps.

---

 Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.