Azure Multi-Factor Authentication Server Issue Caused by Deprecation?

At some point, I started receiving the following errors with my instance of MFA Server which we just noticed yesterday.

[https://imgur.com/a/W5NKiYh](https://imgur.com/a/W5NKiYh)

[https://imgur.com/a/uXd28bF](https://imgur.com/a/uXd28bF)

"Multi-Factor Authentication User Portal is configured to communicate with the Web Service SDK and the Web Service SDK feature has not been purchased."

"Error determining the current master Multi-Factor Authentication Server. The user interface will close."

Did something go corrupt in my instance, or is this the result of the deprecation on 9/30/2024? All SDK authentication calls are still working as expected, but nobody can use the user portal or the MFA Server UI application.

I researched Entra ID for months, and there was seemingly no way to match the workflow we currently have in place with MFA Server on-premises (user authenticates to our custom application which has no association with the Entra ID account, then does MFA with their Entra ID username and Authenticator or OATH token code, **NO INTERACTIVE MICROSOFT LOG IN**). Do I basically just need to build an equivalent user portal and frontend around the SDK?