OIT Services Status

Monitoring: CORRECTION: Current issues with Banner are not related to the OS Patch last weekend; automation tools should be fully functional!

Users are reporting intermittent errors in Banner, and OIT Enterprise Applications Services is aware and communicating with the vendor about a resolution.

Due to the gradual recovery since last night, we are considering this outage to be in a 'monitoring' state. We will make another update as new information becomes available, and at end-of-day today (5:00PM AKST).

Monitoring: CORRECTION: Current issues with Banner are not related to the OS Patch last weekend; automation tools should be fully functional!

Users are reporting intermittent errors in Banner, and OIT Enterprise Applications Services is aware and communicating with the vendor about a resolution.

Due to the gradual recovery since last night, we are considering this outage to be in a 'monitoring' state. We will make another update as new information becomes available, and at end-of-day today (5:00PM AKST).

Identified: Microsoft is discontinuing the M365 A1 Plus license, and some users are being transitioned from the M365 A1 "Plus" license to the M365 A1 license. This results in a loss of access to the desktop version of Office 365 applications, but all users should still be able to use the web-based apps at https://m365.cloud.microsoft/apps/ (requires UA login).

This change affects Crafts & Trades staff, Adjunct/Temporary Faculty, and Emeritus Faculty members. If you're not a member of these groups and are experiencing issues with the Microsoft Office suite, please reach out to your campus's IT helpdesk!

You can find more information about the license change here: https://www.uaf.edu/nooktech/news/microsoft-365-a1-license-changes.php As well as status reports by the license holder, UAA, here: https://status.uaa.alaska.edu/

Due to the longstanding nature of this change and resulting disruption, we will be updating this status only as new information becomes available. We are actively communicating with UAA about the situation, and appreciate your time and understanding as we navigate this unexpected transition. Thank you!

Resolved: Microsoft reports that they've reverted their configuration to its 'last known good' state, and are observing while dependent services recover. UA services that were reported as affected by this outage (NextGen and Touchnet) are functional, and as a result, we will be ending our reporting on the matter.

Further updates directly from Microsoft can be viewed on their statuspage at https://azure.status.microsoft/

Thank you for your time as we followed the resolution of this incident!

Monitoring: As of 1:46pm, Microsoft has stated they ". . . are currently recovering nodes and re-routing traffic through healthy nodes. As recovery progresses, some requests may still land on unhealthy nodes, resulting in intermittent failures or reduced availability until more nodes are fully restored. This recovery effort involves reloading configurations and rebalancing traffic across a large volume of nodes to restore full operational scale. The process is gradual by design, ensuring stability and preventing overload as dependent services recover. We expect continued improvement across affected regions. This means we expect recovery to happen by 23:20 UTC on 29 October 2025"

Full Microsoft status page can be found here: https://azure.status.microsoft/en-us/status

Thank you again for your patience as we continue to monitor this incident. Our next update will follow Microsoft's planned update in two hours.

Identified: As of 11:47am, Microsoft has stated they ". . . anticipate full mitigation within the next four hours as we continue to recover nodes. This means we expect recovery to happen by 23:20 UTC on 29 October 2025. We will provide another update on our progress within two hours, or sooner if warranted."

Full Microsoft status page can be found here: https://azure.status.microsoft/en-us/status

Thank you again for your patience as we continue to monitor this incident. Our next update will follow Microsoft's planned update in two hours.

Identified: As of 11:11am, there is no new update from Microsoft's status page. However, NextGen appears to have restored service to Dynamic Forms, and you should now be able to login to alaska.edu/nextgen like normal.

You can view Microsoft's real-time status reporting here: https://azure.status.microsoft/en-us/status

Thank you again for your patience as we continue to monitor this incident. We will continue to make updates as new information becomes available, and at 30-minute intervals.

Identified: From Microsoft: "Starting at approximately 16:00 UTC, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue.

Current status:

We have initiated the deployment of our last known good configuration, which is expected to complete within 30 minutes. As this deployment progresses, customers should begin to see initial signs of recovery. Once completed, we will begin recovering nodes and routing traffic through these healthy nodes.

Customer configuration changes will remain temporarily blocked while we continue mitigation efforts. We will notify customers once this block has been lifted.

Some customers may also have experienced issues accessing the Azure management portal. We have failed the portal away from AFD to mitigate these access issues. Customers should now be able to access the Azure portal directly, and while most portal extensions are functioning as expected, a small number of endpoints (e.g., Marketplace) may still experience intermittent loading problems.

We do not yet have an ETA for full mitigation, but we will provide another update within 30 minutes, once the deployment has completed.

Customers may also consider implementing failover strategies using Azure Traffic Manager to redirect traffic from Azure Front Door to their origin servers as an interim measure.

This message was last updated at 18:24 UTC on 29 October 2025"

At this time, Azure management itself can be accessed, but the many hosted services are still affected. We will continue to make updates on this incident as new information becomes available, and at 30-minute intervals. Thank you for your time as we do so!

Identified: There has been no new information provided by Microsoft at this time. You can view their realtime status reporting here: https://azure.status.microsoft/en-us/status

Thank you again for your patience as we continue to monitor this incident. We will continue to make updates as new information becomes available, and at 30-minute intervals.

Identified: From Microsoft: "Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state.

We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly.

We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update.

This message was last updated at 17:18 UTC on 29 October 2025"

At this time, Azure management itself can be accessed, but the many hosted services are still affected. We will continue to make updates on this incident as new information becomes available, and at 30-minute intervals. Thank you for your time as we do so!

Investigating: Microsoft is reporting large-scale DNS issues that appear to be affecting the availability and stability of a number of Microsoft-hosted services. This is a vendor-side issue and we are monitoring their public status for updates. Their reporting on the matter can be viewed here: https://azure.status.microsoft/en-us/status and we will be making updates at 30-minute intervals.

Thank you so much for your time and patience during the resolution of this issue.

Resolved: NextGen appears to have put a workaround in place, and their service is operational. You can access your NextGen dashboard at alaska.edu/nextgen

The root Azure outage is still ongoing, and you can view our reporting on the status of that incident here: https://manage.statuspage.io/pages/ld2hkxw36y26/incidents/fgv76pmjw38q

Thank you for your time and patience as we follow the resolution of these issues!

Identified: NextGen has confirmed that the DynamicForms outage is directly related to Azure's ongoing large-scale issues, and we will be reporting on both within the same posting-- you can view that status here: https://status.alaska.edu/incidents/fgv76pmjw38q

Investigating: We have received reports that Nextgen is currently experiencing a complete outage. It appears to be a vendor issue-- the OIT PAWS team is monitoring status updates from the vendor, and we will be making updates at 30-minute intervals.

Thank you for your patience during the resolution of this issue!

Resolved: Touchnet is accessible at this time for both users and technicians.

The root Azure outage is still ongoing, and you can view our reporting on the status of that incident here: https://manage.statuspage.io/pages/ld2hkxw36y26/incidents/fgv76pmjw38q

Thank you for your time and patience as we follow the resolution of these issues!

Identified: Touchnet has confirmed that their outage is directly related to Azure's ongoing large-scale issues, and we will be reporting on both within the same posting-- you can view that status here: https://status.alaska.edu/incidents/fgv76pmjw38q

Investigating: We have received reports that the technician login for Touchnet is currently experiencing issues. We are uncertain as to whether or not this is related to the ongoing Microsoft outage, and UA Financial Systems is reaching out to the vendor for clarification. We will be reporting updates on this outage at 30-minute intervals.

Thank you for your patience during the resolution of this issue!