Adding xms-ids for Communication (#17662)

* Adding xms-ids for Communication

* adding note in readme

Author: agalerrotaru

specification/communication/resource-manager/Microsoft.Communication/preview/2020-08-20-preview/CommunicationService.json

@@ -667,7 +667,10 @@
           "type": "array",
           "items": {
             "$ref": "#/definitions/Operation"
-          }
+          },
+          "x-ms-identifiers": [
+            "name"
+          ]
         },
         "nextLink": {
           "description": "The URL the client should use to fetch the next page (per server side paging).\r\nIt's null for now, added for future use.",
@@ -739,7 +742,11 @@
           "type": "array",
           "items": {
             "$ref": "#/definitions/MetricSpecification"
-          }
+          },
+          "x-ms-identifiers": [
+            "name",
+            "category"
+          ]
         }
       }
     },
@@ -791,7 +798,10 @@
           "type": "array",
           "items": {
             "$ref": "#/definitions/Dimension"
-          }
+          },
+          "x-ms-identifiers": [
+            "name"
+          ]
         }
       }
     },

specification/communication/resource-manager/readme.md

@@ -84,3 +84,8 @@ See configuration in [readme.go.md](./readme.go.md)
 ## Typescript
 
 See configuration in [readme.typescript.md](./readme.typescript.md)
+
+
+## Comments and notes
+x-ms-identifiers will become a requirement on every RP resource. To add it, [check here](https://github.com/Azure/autorest/tree/main/docs/extensions#x-ms-identifiers).
+For more info, reach out to the @changeanalysisteam.