A single-language rule such as “Python for most things” is not the best approach in an Azure environment. Python is a strong choice for AI/ML training, data analysis, and rapid experiments because the tools and libraries are strongest in that space. However, Python should not be the default for all back-end and core platform services, because that creates avoidable cost and risk.
C# is a proven choice for core services such as REST API’s, long-running systems, event-driven processing, and high-throughput workloads. It also matches Azure patterns well for identity, security, hosting, monitoring, and long-term support. Forcing these workloads into Python increases effort in design, testing, operations, and troubleshooting. That leads to slower delivery, higher maintenance, and less reuse of existing .NET components and patterns.
The better mandate is “best tool for the job” with clear defaults. Python is the default for AI/ML training and data-heavy workflows. C# is the default for core services and Azure-native back-end systems where stability, performance, and maintainability are critical. Consistency across the organization is achieved through shared standards, not a single language: common API contracts, message schemas, CI/CD rules, security controls, and logging/metrics/tracing requirements.
A one-language mandate also weakens the organization’s skill base. Developers have different strengths, and that is valuable. Better outcomes come from using expert skills where they fit best, while keeping strong rules for quality, security, and integration. Supporting both Python and C# reduces delivery risk, improves speed, and protects long-term support, without forcing unnecessary rewrites or lowering productivity.