Since they decided they are done with C, Microsoft has been cleaning up Windows code to make their code compliant with the C subset of C++.
Since Windows Longhorn failure, with Vista COM got the main API role for the components that were originally designed to be written in .NET.
Which lead to the design of UWP as improved COM, using the ideas they originally had for Ext-VOS, but decided to create .NET instead.
https://www.reddit.com/r/cpp/comments/4oruo1/windows_10_code...
I really wish the Visual Studio team would give C a bit more love. Getting at least full C99 support in is most likely less work than any random C++17 feature.
ANSI C++14 requires C99 library, while ANSI C++17 upgraded it to C11.
Microsoft has contributed to improve clang on Windows for those that still want to keep on using C, but then good luck accessing COM and .NET APIs from C, it is possible but I wouldn't do it for fun.
Even the new C runtime library is actually written in C++.
D3D11's C API works fine (that's the only Windows API I care about apart from the usual Win32 windowing stuff), but already D3D12 let that rot and is only usable from C with workarounds (doesn't matter though since D3D12 is fairly niche).
All in all it's a shame though because the newer C features are much more sane and useful than anything in C++14 or C++17.
There is no written rule that C++ compilers are obliged to be C compilers as well.
Again, as C++ compiler, they are only required to be as compatible with C code as ANSI C++ requires.