You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/raw-id-use-cases.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,9 +23,9 @@ CommunicationIdentifier has the following advantages:
23
23
- Provides good auto-complete in IDEs.
24
24
- Allows using a switch case by type to address different application flows.
25
25
- Allows restricting communication to specific types.
26
+
- Allow access to identifier details and use them to call other APIs (such as the Microsoft Graph API) to provide a rich experience for communication participants.
26
27
27
28
On top of this, the *CommunicationIdentifier* and the derived types (`MicrosoftTeamsUserIdentifier`, `PhoneNumberIdentifier`, etc.) can be converted to its string representation (Raw ID) and restored from the string, making the following scenarios easier to implement:
28
-
- Extract identifier details from Raw IDs and use them to call other APIs (such as the Microsoft Graph API) to provide a rich experience for communication participants.
29
29
- Store identifiers in a database and use them as keys.
30
30
- Use identifiers as keys in dictionaries.
31
31
- Implement intuitive REST CRUD APIs by using identifiers as key in REST API paths, instead of having to rely on POST payloads.
@@ -37,15 +37,22 @@ On top of this, the *CommunicationIdentifier* and the derived types (`MicrosoftT
0 commit comments