简体   繁体   English

Azure AD 或 Teams Provisioning 中的哪些字段是传递到 Teams App 消息传递端点的 JSON 中entities.country/locale 信息的来源?

[英]What fields in Azure AD or Teams Provisioning are the source of entities.country/locale info in the JSON delivered to Teams App messaging endpoint?

Microsoft Teams <-> Azure AD Bot Registration w/ Teams Channel <-> Custom Teams App/Bot Messaging End Point using Bot Framework. Microsoft Teams <-> Azure AD Bot 注册 w/ Teams 频道 <-> 使用 Bot Framework 的自定义 Teams 应用程序/机器人消息传递端点。

We have a Custom Teams App built using Microsoft Bot Framework.我们有一个使用 Microsoft Bot Framework 构建的自定义团队应用程序。 We wish to use some of geo attributes provided by Teams to the messaging end point in the incoming messaging delivered from Teams to our chat bot, in particular entities.country and entities.locale (These are described in Microsoft Schema https://docs.microsoft.com/en-us/microsoftteams/platform/resources/bot-v3/bot-conversations/bots-conversations#full-inbound-schema-example and excerpted below)我们希望将 Teams 提供的一些地理属性用于从 Teams 传递到我们的聊天机器人的传入消息中的消息传递端点,特别是 entity.country 和 entity.locale(这些在 Microsoft Schema https://docs 中进行了描述。 microsoft.com/en-us/microsoftteams/platform/resources/bot-v3/bot-conversations/bots-conversations#full-inbound-schema-example并摘录如下)

在此处输入图像描述

We believe that these attributes are sourced from Azure AD User Profile, but would like to know which field.我们认为这些属性来自 Azure AD 用户配置文件,但想知道是哪个字段。 And if not from Azure AD data which data fields or configurations.如果不是来自 Azure AD 数据,哪些数据字段或配置。

We have a customer where the Country (CO and C) are properly set as a country other than US, however Teams Bot Conversation JSON reports US as the country in entities.country and not the country configured in Azure AD.我们有一个客户,其中国家(CO 和 C)被正确设置为美国以外的国家,但是 Teams Bot Conversation JSON 在entities.country 中将美国报告为国家,而不是在 Azure AD 中配置的国家。 (Teams tenant appears to be hosted in Western Europe, so somehow during the Teams license provisioning perhaps some country attributes are getting over ridden from their values in Azure AD). (Teams 租户似乎托管在西欧,因此在 Teams 许可配置期间,某些国家/地区属性可能已超出 Azure AD 中的值。)

entities.country and entities.locale get populated from the Teams settings. entity.country 和 entity.locale 从 Teams 设置中填充。 We tried as below.我们尝试如下。

  1. When the APP language is English(US), we got the below payload at the bot endpoint.当 APP 语言为英语(美国)时,我们在 bot 端点获得了以下有效负载。

在此处输入图像描述

"entities": [
        {
            "locale": "en-US",
            "country": "US",
            "platform": "Web",
            "timezone": "Asia/Calcutta",
            "type": "clientInfo"
        }
    ]
  1. When the APP language is English(India), we got the below payload at the bot endpoint.当 APP 语言为英语(印度)时,我们在 bot 端点获得了以下有效负载。

在此处输入图像描述

"entities": [
        {
            "locale": "en-IN",
            "country": "IN",
            "platform": "Web",
            "timezone": "Asia/Calcutta",
            "type": "clientInfo"
        }
    ]

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 带有 Azure AD 身份验证的 SaaS 应用程序作为带有 App Studio 的 MS Teams 应用程序 - SaaS Application with Azure AD authentication as MS Teams App with App Studio Azure AD 与机器人框架/团队的集成 - Azure AD integration with Bot Framework / teams 广告连接 - Teams 中的哪些数据将丢失 - Ad connect - what data from Teams will be missing 在应用工作室中创建聊天机器人时,将 MS Teams Bot 链接到 Azure AD 应用 - Link MS Teams Bot to Azure AD app when creating chatbot in app studio Azure AD B2C 和 MS Teams 应用(机器人 + 选项卡)身份验证 - Azure AD B2C and MS Teams app (bot + tab) auth 如何使用身份服务器 3 和 Microsoft 团队应用程序使用 Azure AD 令牌进行身份验证 - How to authenticate using Azure AD token using identity server 3 and microsoft teams app 是否可以将经过身份验证的 Azure AD 用户(通过 ROPC)重定向到 Microsoft Teams? - Is it possible to redirect authenticated Azure AD users (by ROPC) to Microsoft Teams? 如何针对Azure AD对MS Teams用户进行身份验证 - How to Authenticate MS Teams User Against Azure AD 使用应用程序注册的 Azure AD 自动用户预配 - Azure AD Automatic User Provisioning With App registartion 在另一个 azure 租户中注册的团队中上传自定义应用程序 - Upload custom app in teams registered in another azure tenant
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM