User Profile
DavidB2390
Copper Contributor
Joined 3 years ago
User Widgets
Recent Discussions
Issue with Empty From.User Property in Microsoft Graph API Chat Messages
Issue Summary: I’m working with the Microsoft Graph API to retrieve chat messages, and I’m encountering an issue where theFrom.Userproperty is consistently empty. Despite having the necessary permissions (User.Read.AllandChat.Read.All), the API response does not include the expected user information in theFrom.Userfield. Details: API Permissions:User.Read.All,Chat.Read.All Endpoint:Retrieving chat messages usingGet-MgChatMessage Observed Behavior:TheFrom.Userproperty is always empty, with bothDisplayNameandIdfields returningnull. Steps Taken: Verified API permissions. Inspected the raw JSON response, which also shows emptyFrom.Userfields. Checked the Microsoft Graph API documentation for any notes on this behavior. Example Response: { "From": { "Application": { "DisplayName": null, "Id": null }, "Device": { "DisplayName": null, "Id": null }, "User": { "DisplayName": null, "Id": null } }, "CreatedDateTime": "2024-09-24T15:11:50Z", "Id": "1727190710868", "Body": { "Content": "<systemEventMessage/>", "ContentType": "html" } } Has anyone encountered a similar issue or can provide insights on why theFrom.Userproperty might not be populated? Thanks88Views0likes0CommentsWhen is SCSM 2022 going to support the Orchestrator 2022 API?
Not in UR2 - will it be in UR3? Seems kind of a basic requirement that for a new release of the Service Manager product that the integrations between the products work.... And we never got SM to talk ok to an install of the the 2019 API on a 2022 install of Orchestrator which was the suggested workaround. 'Service Manager (SM) console doesn't detect Orchestrator 2022 installation because the Connector for the new Web API is yet to be released.' Update Rollup 2 for System Center 2022 Orchestrator - Microsoft Support307Views0likes0CommentsAAD devices can't communicate with the CMG
Hybrid domain joined computers can e.g. download software from the CMG but AAD computers can't. The AAD devices have root and intermediate certs via PKI installed and as a test I installed the actual cmg cert (from windows certificate authority service) on an AAD device and checked that the certificate chain is ok for the device. The root and intermediate certs were also specified when creating the CMG. Connection analyser is green ticks everywhere. The site is HTTPS only and we use certificates on all devices. The CMG has been recreated from scratch using a scale set and with new app registrations and we use a cname dns entry to map to Azure CMG dns name, The devices appear to install ok via autopilot co-management using this script: CCMSETUPCMD="CCMHOSTNAME=ourcmg.company.com/CCM_Proxy_MutualAuth/xxx57594037927xxx SMSSiteCode=555" The main errors are these in ccmMessaging log: Failed to get CCM access token while token auth is required. Error 0x87d00231 [CCMHTTP] ERROR: URL=http://222.178.203.72:19005/whst/63/=ntqblfzbnloZmxzbnl//CCM_Proxy_MutualAuth/xxx57594037927xxx/ccm_system/request, Port=443, Options=448, Code=12175, Text=ERROR_WINHTTP_SECURE_FAILURE Post to https://ourcmg.company.com/CCM_Proxy_MutualAuth/xxx57594037927xxx/ccm_system_windowsauth/request failed with 0x87d00231. Thanks for any ideas - the case has been with Microsoft support for weeks and no answer as yet.680Views0likes1Comment