Please find the troubleshoot step as mention in below
- URL Encoding: The message ID contains special characters, including the "/" character, which need to be URL encoded when used in a URL. In a URL, the "/" character is reserved as a path segment delimiter, so it must be percent-encoded
- Correctly Format the API Request: Ensure the message ID is properly encoded in your API request
- Retry the API Request: Once the message ID is properly encoded, retry the API request with the updated URL. 4.Access Permissions: Ensure that the token you are using has the appropriate permissions to access the message. 5.Check for API Changes: Sometimes, API endpoints or requirements change. Make sure to check for any recent updates or changes in the Microsoft Graph API that might affect how you should format your request.