No new occurence of the issue has been observered since the fix was deployed.
Everything is operational again.
We will deploy an application fix at a later time as a more permanent solution.
Updated Analysis/Description of the Issue:
The initial assumption that the cause was due to an underlying Azure reconfiguration was only partially correct.
The Azure reconfiguration happened 3 months ago, enforcing the URL limit to become 2048 chars (which is documented default, so basically they fixed a bug).
This did not immediately have any effect.
On January 9th, Vipps deployed a change causing their order/agreement draft response to contain additional characters. For some tenants, this tipped the generated URLs above the 2048 character limit.
Our current solution has been to reconfigure the limit, but we are working on a more permanent solution where such changes to third parties will not interrupt the workflow again.
Sorry for any inconveniences this may have caused.