That is very disappointing! Why was that done?
I knew people were upset about something to do with MS Access databases and I had always assumed it had to do with Esri dropping support for personal geodatabases; because I don't use personal geodatabases I hadn't paid much attention. I had not realized that OLE DB for ODBC connections were dropped in Pro!
The MySQL data is used in real-time joins, so transforming and importing is not practical. I only have one table that I have been using this way in GIS currently, but we were planning more. I can see how other organizations could have many connections to such data and this could be quite a hardship. Guess I'll have to stay with ArcMap until I find a solution, or this functionality is brought to Pro. But I can't stay with ArcMap, because I need the Utility Network . . .
That thread is referring specifically to Microsoft Access (accdb) support. If that were solved, would it solve my issue with MySQL? If so, I'll add my use case, but I don't want to be off-topic.
Cheryl