Hi,
I am currently checking out if our business can start to use Microsoft Bookings as our internal tool for planning meetings from bookers to staff. To do so we need to have the Power Automate running for handling creations, updates and deletions of meetings.
The Power Automate comes with a standard connector "Microsoft Bookings (preview)". I have seen quite a few blog posts and examples of how to use it, however I cant get started cause after creating the connection with my account (which works fine) I go to start the flow, the trigger can see my connection fine, but when i use the dropdown to select the booking of choice I get hit by the error message:
The dynamic invocation request failed with error: "Failed to get onbehalfof access token: connectionId=microsoftbookings, message={\"error\":\"invalid_grant\",\"error_description\":\"AADSTS50013: Assertion failed signature validation. [Reason - Key was found, but use of the key to verify the signature failed., Thumbprint of key used by client: 'ABEDB77DA95EBD98610F7866F4241B90FE4C4325', Found key 'Start=03/06/2024 17:03:32, End=03/06/2029 17:03:32', Please visit the Azure Portal, Graph Explorer or directly use MS Graph to see configured keys for app Id '00000000-0000-0000-0000-000000000000'. Review the documentation at https://docs.microsoft.com/en-us/graph/deployments to determine the corresponding service endpoint and https://docs.microsoft.com/en-us/graph/api/application-get?view=graph-rest-1.0&tabs=http to build a query request URL, such as 'https://graph.microsoft.com/beta/applications/00000000-0000-0000-0000-000000000000']. Trace ID: 327f55e3-ffd5-4193-bd6f-78220a177500 Correlation ID: a6fb7e8b-958d-4cd8-b984-152d8e4813ef Timestamp: 2024-04-04 15:15:32Z\",\"error_codes\":[50013],\"timestamp\":\"2024-04-04 15:15:32Z\",\"trace_id\":\"327f55e3-ffd5-4193-bd6f-78220a177500\",\"correlation_id\":\"a6fb7e8b-958d-4cd8-b984-152d8e4813ef\",\"error_uri\":\"https://login.windows.net/error?code=50013\"}".
Now first when I attempted this earlier today I assumed it might just be a glitch in the service but now I attempted later. From what I get from this message is that the dates are all messed up in the keys. I added this connector right now today 04/04/2024 17:03:32, yet the key is having a start date registered 03/06/2024 which is about two months in the future I assume?
To me this clearly seems like theres an ongoing bug with the connector - I would originally think this had something to do with the oAuth approval process, but I can add many other connectors just fine, its just the Microsoft Bookings (Preview) connector that seems to fail.
Ive searched through a couple forum resources, and I have removed the connector many times and reconnected it, I have attempted several browsers with and without incognito. I have cleared my browsers caches. I cannot make it work.
Is there any ideas to solve this and or where would I report the bug if it continues to happen the next couple days?
