This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Sinds 2020-06-02 02:57:32 the request id and operation_id is changed for APIM. I use this id for correlation.
The id is not a Guid anymore, what is the way to go with this?
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 38%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ%3C/text%3E%3C/svg%3E)
Hello anonymous user ,Just checking back, could you please let us know if you need further help in this matter.
Hello anonymous user, Sorry for the delay in response.
The missing dashes are by design behavior. Product team statement about it is the following
Application Insights correlation protocol specification doesn't define operation id format, neither do we, so no assumptions should be made regarding the format.
Please let us know if you need further help in this matter.
Hello anonymous user ,Just checking back, could you please let us know if you need further help in this matter.