microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Unable to deploy PolicyRecordingBot.

Open
#535 5 comments 0 reactions 0 assignees View on GitHub

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
Unable to deploy PolicyRecordingBot.

Code Snippet

Expected behavior
Deploy PolicyRecordingBot to Cloud Services (extended support)

Graph SDK (please complete the following information):

Call ID
Provide the list call ids that encountered this issue. Include the time in UTC/GMT when these call have occurred.

Logs

Additional context
Hello.
I'm trying to make sure PolicyRecordingBot is working.
But it fails to deploy.
Currently, newly created subscriptions are
Cloud Services (classic) is not supported, so I have to choose Cloud Services (extended support).
Have you confirmed that it works there?

Cloud.cscfg and ServiceDefinition.csdef provided by Github are sufficient?
Also, there seems to be no SampleGraphBotProduction1.azurePubxml, where is it?

-------こんにちは
PolicyRecordingBotの動作確認しようとしていますが
でも、デプロイに失敗します
現在新規に作成したサブスクリプションでは
Cloud Services (classic) はサポートされないため Cloud Services (extended support) 一択なのですが
そこでの、動作確認はできていますか?

ServiceConfiguration.Cloud.cscfg、ServiceDefinition.csdefはGithubで提供されているもので十分でしょうか
また、SampleGraphBotProduction1.azurePubxmlがないようですが、どこにありますか

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the PolicyRecordingBot deployment configuration, including ServiceConfiguration.Cloud.cscfg and ServiceDefinition.csdef, and investigate the missing SampleGraphBotProduction1.azurePubxml mentioned in the issue. Reproduce the deployment against Cloud Services (extended support), recording the deployment logs and call IDs. Done means the bot deploys successfully in that environment or the required configuration is identified.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.