ACS SMS, removing/adjusting message ID examples and asking customers not to build their logic on top of that

Author: Kirill Linnik

articles/communication-services/concepts/analytics/logs/sms-logs.md

@@ -89,9 +89,9 @@ Communication Services offers the following types of logs:
 | `SdkType` | The SDK type used in the request. |
 | `PlatformType` | The platform type used in the request. |
 | `Method` | The method used in the request. |
-|`NumberType`| The type of number, the SMS message is being sent from. It can be either **LongCodeNumber**, **ShortCodeNumber**, or **DynamicAlphaSenderID**.|
-|`MessageID`| Represents the unique messageId generated for every outgoing and incoming message. Find the MessageId in the SMS API response object. |
-|`Country`| Represents the countries/regions where SMS messages are sent to or received from. |
+| `NumberType` | The type of number, the SMS message is being sent from. It can be either **LongCodeNumber**, **ShortCodeNumber**, or **DynamicAlphaSenderID**.|
+| `MessageID` | Represents the unique message ID generated for every outgoing and incoming message. Find the MessageId in the SMS API response object. The format of message ID returned by this API is considered an internal implementation detail and is subject to change without notice. Clients must treat message ID as opaque identifiers and must not parse, infer structure, or build logic based on their format or content.|
+| `Country` | Represents the countries/regions where SMS messages are sent to or received from. |
 
 #### Example SMS sent log
 
@@ -118,7 +118,7 @@ Communication Services offers the following types of logs:
         "SdkType": "azsdk-net-Communication.Sms",
         "PlatformType": "Microsoft Windows 10.0.17763",
         "Method": "POST",
-        "MessageId": "Outgoing_20230118181300ff00e5c9-876d-4958-86e3-4637484fe5bd_noam",
+        "MessageId": "ff00e5c9-876d-4958-86e3-4637484fe5bd",
         "Country": "US"
       }
     ]
@@ -149,7 +149,7 @@ Communication Services offers the following types of logs:
         "SdkType": "",
         "PlatformType": "",
         "Method": "POST",
-        "MessageId": "Outgoing_20230118181300ff00e5c9-876d-4958-86e3-4637484fe5bd_noam",
+        "MessageId": "ff00e5c9-876d-4958-86e3-4637484fe5bd",
         "Country": "US"
       }
     ]
@@ -180,7 +180,7 @@ Communication Services offers the following types of logs:
         "SdkType": "",
         "PlatformType": "",
         "Method": "POST",
-        "MessageId": "Incoming_2023011818121211c6ee31-63fe-477c-8d51-f800543c6694",
+        "MessageId": "11c6ee31-63fe-477c-8d51-f800543c6694",
         "Country": "US"
       }
     ]
@@ -189,4 +189,4 @@ Communication Services offers the following types of logs:
 
 ## Related articles
 
- [SMS FAQ](/azure/azure-monitor/overview#frequently-asked-questions)
+ [SMS FAQ](/azure/azure-monitor/overview#frequently-asked-questions)

articles/communication-services/how-tos/event-grid/local-testing-event-grid.md

@@ -48,11 +48,11 @@ http://localhost:7071/runtime/webhooks/EventGrid?functionName={functionname}
     ```json
 
     {
-      "id": "Incoming_20200918002745d29ebbea-3341-4466-9690-0a03af35228e",
+      "id": "d29ebbea-3341-4466-9690-0a03af35228e",
       "topic": "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourcegroups/acse2e/providers/microsoft.communication/communicationservices/{communication-services-resource-name}",
       "subject": "/phonenumber/15555555555",
       "data": {
-        "MessageId": "Incoming_20200918002745d29ebbea-3341-4466-9690-0a03af35228e",
+        "MessageId": "d29ebbea-3341-4466-9690-0a03af35228e",
         "From": "15555555555",
         "To": "15555555555",
         "Message": "Great to connect with Azure Communication Services events",
@@ -79,4 +79,4 @@ http://localhost:7071/runtime/webhooks/EventGrid?functionName={functionname}
 
     ![Screenshot of Postman send button.](media/postman-send.png)
 
-    At this point, an event should trigger in your Azure Function. You can verify the event by looking at the execution of your Azure Function. You can then validate that the function is doing its job correctly.
+    At this point, an event should trigger in your Azure Function. You can verify the event by looking at the execution of your Azure Function. You can then validate that the function is doing its job correctly.

articles/communication-services/how-tos/event-grid/media/postman-body.png

@@ -201,6 +201,6 @@ The final output should resemble the following:
 Retrieving new Access Token, using Service Principals
 Retrieved Access Token: ey..A
 Sending SMS using using Service Principals
-Sms id: Outgoing_202104...33f8ae1f_noam
+Sms id: ...
 Send Result Successful: true
 ```

articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-java.md

@@ -158,6 +158,6 @@ With everything complete, you can run the file by entering `node index.js` from
     Retrieving new Access Token, using Service Principals
     Retrieved Access Token: ey...Q
     Sending SMS using Service Principals
-    SMS ID: Outgoing_2021040602194...._noam
+    SMS ID: ...
     Send Result Successful: true
-```
+```

articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-js.md

@@ -161,6 +161,6 @@ You should now be able to run your application, using `dotnet run` from your app
 Retrieving new Access Token, using Service Principals
 Retrieved Access Token: ey....
 Sending SMS using Service Principals
-Sms id: Outgoing_..._noam
+Sms id: ...
 Send Result Successful: True
-```
+```

articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-net.md

@@ -138,6 +138,6 @@ With everything complete, you can run the file by entering `python authenticatio
     Retrieving new Access Token, using Service Principals
     Retrieved Access Token: ey...Q
     Sending SMS using using Service Principals
-    SMS ID: Outgoing_2021040602194...._noam
+    SMS ID: ...
     Send Result Successful: true
-```
+```

articles/communication-services/quickstarts/identity/includes/active-directory/service-principal-python.md

@@ -26,11 +26,11 @@ The `SMSReceived` event generated when an SMS is sent to an Azure Communication
 
 ```json
 [{
-  "id": "Incoming_20200918002745d29ebbea-3341-4466-9690-0a03af35228e",
+  "id": "d29ebbea-3341-4466-9690-0a03af35228e",
   "topic": "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourcegroups/acse2e/providers/microsoft.communication/communicationservices/{communication-services-resource-name}",
   "subject": "/phonenumber/15555555555",
   "data": {
-    "MessageId": "Incoming_20200918002745d29ebbea-3341-4466-9690-0a03af35228e",
+    "MessageId": "d29ebbea-3341-4466-9690-0a03af35228e",
     "From": "15555555555",
     "To": "15555555555",
     "Message": "Great to connect with Azure Communication Services events",
@@ -42,6 +42,8 @@ The `SMSReceived` event generated when an SMS is sent to an Azure Communication
   "eventTime": "2020-09-18T00:27:47Z"
 }]
 ```
+> [!NOTE] 
+> The format of `MessageId` returned by this API is considered an internal implementation detail and is subject to change without notice. Clients must treat message IDs as opaque identifiers and must not parse, infer structure, or build logic based on their format or content.
 
 To start generating events, configure Azure Event Grid to use your Azure Communication Services resource.
 
@@ -80,4 +82,4 @@ If you have a new toll-free number and want to send a [high volume of SMS messag
 > [Phone number types](../../concepts/telephony/plan-solution.md)
 
 > [!div class="nextstepaction"]
-> [Learn more about SMS](../../concepts/sms/concepts.md)
+> [Learn more about SMS](../../concepts/sms/concepts.md)

articles/communication-services/quickstarts/sms/receive-sms.md

@@ -9,7 +9,7 @@ ms.author: vikramdh
 
 # Azure Communication Services - SMS events
 
-This article provides the properties and schema for communication services SMS events. For an introduction to event schemas, see [Azure Event Grid event schema](event-schema.md).
+This article provides the properties and schema for communication services SMS events. For an introduction to event schemas, see [Azure Event Grid event schema](event-schema.md).
 
 ## Events types
 
@@ -30,11 +30,11 @@ This section contains an example of what that data would look like for each even
 
 ```json
 [{
-  "id": "Outgoing_202009180022138813a09b-0cbf-4304-9b03-1546683bb910",
+  "id": "8813a09b-0cbf-4304-9b03-1546683bb910",
   "topic": "/subscriptions/{subscription-id}/resourceGroups/{group-name}/providers/microsoft.communication/communicationservices/{communication-services-resource-name}",
   "subject": "/phonenumber/15555555555",
   "data": {
-    "messageId": "Outgoing_202009180022138813a09b-0cbf-4304-9b03-1546683bb910",
+    "messageId": "8813a09b-0cbf-4304-9b03-1546683bb910",
     "from": "15555555555",
     "to": "+15555555555",
     "deliveryStatus": "Delivered",
@@ -63,11 +63,11 @@ This section contains an example of what that data would look like for each even
 
 ```json
 [{
-  "id": "Incoming_20200918002745d29ebbea-3341-4466-9690-0a03af35228e",
+  "id": "d29ebbea-3341-4466-9690-0a03af35228e",
   "topic": "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourcegroups/acse2e/providers/microsoft.communication/communicationservices/{communication-services-resource-name}",
   "subject": "/phonenumber/15555555555",
   "data": {
-    "messageId": "Incoming_20200918002745d29ebbea-3341-4466-9690-0a03af35228e",
+    "messageId": "d29ebbea-3341-4466-9690-0a03af35228e",
     "from": "15555555555",
     "to": "15555555555",
     "message": "Great to connect with Azure Communication Services events",
@@ -82,4 +82,4 @@ This section contains an example of what that data would look like for each even
 ```
 
 ## Next steps
-See the following tutorial:[Quickstart: Handle SMS and delivery report events](../communication-services/quickstarts/sms/handle-sms-events.md).
+See the following tutorial:[Quickstart: Handle SMS and delivery report events](../communication-services/quickstarts/sms/handle-sms-events.md).