microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Deploying PolicyRecordingBot to Azure
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Describe the issue
After lots of successful local testing I have now deployed my modified PolicyRecordingBot implementation to Azure. However, my deployment is done via a Azure Dev Ops Build pipeline and release (pipeline). However my bot won't start due to the following error:-
Could not load file or assembly 'Microsoft.Rtc.Internal.Media.MediaApi.dll' or one of its dependencies. The specified module could not be found. at Microsoft.Skype.Bots.Media.MediaApiPlatformWrapper.Initialize() at Microsoft.Skype.Internal.Bots.Media.InternalMediaPlatform.Initialize(MediaPlatformSettings settings, IConfigurationManager configurationManager, Boolean isTest) at Microsoft.Graph.Communications.Calls.Media.MediaCommunicationsClientBuilderExtensions.SetMediaPlatformSettings(ICommunicationsClientBuilder statefulClientBuilder, MediaPlatformSettings mediaSettings)
Code Snippet
Not applicable.
Expected behavior
I'd expect my bot to spin up exactly as it does when ran locally on my PC
Graph SDK (please complete the following information):
- Still not sure how to determine which version of the 'sdk' i'm using
Call ID
Not applicable.
Logs
Not applicable.
Additional context
None
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Azure Dev Ops build and release pipeline and the MediaApiPlatformWrapper.Initialize() failure shown in the deployment error. Compare the deployed environment with the local setup, focusing on Microsoft.Rtc.Internal.Media.MediaApi.dll and its dependencies; done means the bot starts successfully on Azure as it does locally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100