3.3 Save somewhere Microsoft App ID (App ID). To get App Secret
you need to proceed to the Manage ling near the Microsoft App ID pane.
You will need both during your DeepPavlov skill/component REST service start.

Web App Bot channels configuration

4.1 Microsoft Bot Framework allows your bot to communicate
to the outer world via different channels. To set up these channels
navigate to the Channels menu, select channel and follow further instructions.

MS Bot Framework sends messages from all channels to the https endpoint
which was set in the Web App Bot connection configuration section.

You should deploy DeepPavlov skill/component REST service on this
endpoint or terminate it to your REST service. Full REST endpoint URL
can be obtained by the swagger apidocs/ endpoint. We remind you that Microsoft Bot Framework requires https endpoint
with valid certificate from CA.

Each DeepPavlov skill/component can be made available for MS Bot Framework
as a REST service by:

If you redirect requests to your skills service from some https endpoint, you may want to run it in http mode by
omitting --https, --key, --cert keys.

Optional -d key can be provided for dependencies download
before service start.

Optional -p key can be provided to override the port value from a settings file.

Optional --stateful flag should be provided for stateful skills/components.

Optional --multi-instance can be provided if you wish to raise separate skill/component instance
for each conversation.

You should use --no-default-skill optional flag if your component implements an interface of DeepPavlov Skill
to skip its wrapping with DeepPavlov DefaultStatelessSkill.

REST service properties (host, port) are provided in deeppavlov/utils/settings/server_config.json. You can also store your
app id and app secret in appropriate section of server_config.json. Please note, that all command line parameters
override corresponding config ones.