| Previous | Next |
| PEER_E_INVALID_RECORD | PEER_E_PASSWORD_DOES_NOT_MEET_POLICY |
PEER_E_NOT_AUTHORIZED
Which peer contract was rejected
PEER_E_NOT_AUTHORIZED — HRESULT 0x80632020 means that the authenticated group member lacks the role or record ownership authority required for the requested operation. The relevant API boundary includes PeerGroupSetProperties, record delete/update and PeerGroupIssueCredentials.
Minimum diagnostic packet
| Item | Evidence |
|---|---|
| Raw input | Preserve member identity, GMC roles, record creator, requested action, group properties and the credential chain used for the connection. |
| Owning context | Record the Windows user, process integrity, graph or group handle, database path and selected cloud. |
| Previous success | Save the last successful create, open, enumerate, parse, register or sign-in result that produced the object. |
| Result order | Retain the first HRESULT so cleanup failures do not replace the code that rejected the request. |
Focused reproduction
Perform the operation as the record creator or a member with the documented administrator role and compare with the failing member.
Why the comparison code is different
PEER_E_CONNECTION_NOT_AUTHENTICATED differs because not-authorized occurs after an identity is recognized; not-authenticated means secure connection establishment failed.
Recommended change
Issue appropriate credentials or redesign the operation around allowed ownership rules; do not weaken invitation trust checks.
Technical references
Looking for a different code? Search another status or error code.