Repository navigation
Record group chat lookup timing and which forms of address find a user - #23
Merged
Merged
Conversation
Section 9 attributes its count of 6 group chats to the signed-in sender, but that read-only run signed in as one of the recipient accounts, and the section has no timing for the two lookup calls. Say which account the count came from, add the timing of the Chat.Read and Chat.ReadBasic calls, and list what the timing leaves open.
The research notes list the module's own New-MgChat -Members call as unverified, and say nothing about what OneDrive names a chat attachment whose name contains a plus sign. Add the 2026-10-01 measurements: a Group send with no matching chat creates a group chat with exactly the sender and recipients, a second send finds it, a member's email can differ in letter case from the address given and still matches, and a recipient who leaves a chat drops out of the members the sender's listing returns. Record that a plus sign in an attachment name is kept in OneDrive and in Teams.
The research notes list the UPN mismatch and the alias failure as untested inferences, and say nothing about which forms of a user's address Graph accepts when a chat is created, an attachment is shared, or mail is sent. Add section 10 with the measurements from 2026-10-01 and 2026-10-02: a UPN and a primary email that is not the UPN both find the user for a chat, a secondary address that was never a UPN fails in New-MgChat with a 404 while the module's warning names the recipient, an attachment can be shared with a UPN, and mail to a UPN is delivered. Cite the Entra documentation that always adds a mailbox user's UPN as a proxy address, and say why the results still do not show whether Graph resolves a primary email that is not the UPN, and what would settle it. In section 9, record the duplicate group chat that a recipient given by a UPN gets, and point to section 10 for the forms of address.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Research notes only, all in
Research_Notes/Microsoft-Graph-Behavior.md, from live testing between 2026-09-30 and2026-10-02:
count. It adds live results for a group chat being created and then reused, a member
emaildiffering in lettercase, a recipient leaving a chat, and a recipient given by a UPN that differs from their primary email, who gets
a new group chat on every send while
Errorstays empty.+in a chat attachment's name is kept in OneDrive and in Teams.UPN, both find the user for a chat; a secondary address that was never a UPN fails with a 404; an attachment can
be shared with a UPN; and mail to a UPN is delivered, because Microsoft Entra ID always adds a mailbox user's UPN
as a proxy address. It also says what is still unverified: whether Graph resolves a primary email that is not
the UPN, or was still resolving a former UPN, and what test would settle it.
No module file changes, so there is no changelog entry.
Live testing used Microsoft Graph with a delegated sign-in for chat and application permissions for mail, and sent
messages and small test files only to three accounts the tester controls. One of those accounts had its UPN
changed in Microsoft Entra ID for the tests.
Release classification
Checklist
develop, ormainfor a hotfixCHANGELOG.mdhas an entry in the right section under[Unreleased](added if missing), or the change is not user-visible.\Tests\Invoke-Tests.ps1passes