hi Randy,
a scheduled maintenance shouldn't break your service, and getting 404 errors across the board is a severe symptom. this isn't something you can "undo" yourself; it requires immediate investigation by microsoft.
a 404 error after maintenance strongly suggests that the gateway's configuration was corrupted or reverted during the update process. the api endpoints, policies, or the gateway's routing table might have been affected.
your first and most urgent step is to contact azure support immediately. since your service is down, this qualifies as a severe production outage. when you create the support ticket, provide the exact timestamp of the maintenance operation from your activity log and clearly state that all endpoints are returning 404 afterward.
while you wait for support, here are two things you can quickly check in the azure portal. check the "diagnose and solve problems" blade for your api management service. it might have a built in detector for configuration or gateway issues that can provide more details. review your api's "settings". verify that the apis are still showing as present and that their path settings haven't been accidentally changed or cleared.
however, given the nature of the issue, a support ticket is your definitive path to resolution. the backend engineers can investigate the maintenance operation's logs and restore the correct configuration.
this is a platform incident. open a high severity support ticket with microsoft right away, providing the maintenance timestamp and the fact that you're getting 404s
regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer