The Django team hasn't moved toward IIS integration, and given the project's direction and community focus, it’s unlikely they ever will. Django continues to be deeply tied to WSGI/ASGI and thrives in *nix-based environments.
Windows Subsystem for Linux (WSL2) is now extremely solid. Many developers use it to run full Django stacks on Windows without touching IIS at all.
Docker + Windows support is better than ever, so you can package your Django app in a Linux container and deploy it consistently, even on Windows infrastructure.
Azure App Services and Azure Container Instances fully support Django (via WSGI/ASGI), so if you're in the Microsoft ecosystem, that’s now a Python-friendly path.
Microsoft itself is more Python-friendly now than ever before — VS Code, Azure, and even the official Python extension teams are heavily invested in the Python community.
So, having mentioned that, the best options for you are:
Stick with ASP.NET and IIS for native Windows harmony (which is still a good option).
Use Django with Docker, WSL2, or reverse-proxying with NGINX/Apache even on Windows.
Or, deploy Django externally (e.g. on Linux VMs or containers) and integrate with your Windows-based systems via APIs.