STOP Making these Azure Development Mistakes – Lessons Learned from Real-World Experiences

In this episode of Azure on Air, Lex discusses with Toon Vanhoutte, CTO at Noest, to discuss common mistakes people make when developing and deploying Azure solutions. Toon shared his own experiences, as well as lessons learned from others in the community, to help us avoid costly mistakes and improve our Azure integration skills.

Mistake 1: Not Considering Cost Management

Toon shared a personal story about a costly mistake he made when designing an Azure solution. He created an endless loop that resulted in a $6,000 bill. The lesson learned is to always consider cost management and set up budget alerts to prevent similar mistakes.

Mistake 2: Using User Accounts for Integration

Ricardo’s case highlighted the importance of not using user accounts for integration. When his account was compromised, the integration started failing, and notifications didn’t work. The lesson learned is to use managed identities and service accounts instead of user accounts for integration.

Mistake 3: Not Testing Connectors Thoroughly

Bill’s experience taught us the importance of thoroughly testing connectors before using them in production. He designed a solution using Logic Apps Standard, but it didn’t support the peek-lock pattern, which caused issues. The lesson learned is to always test connectors and consider their limitations before using them.

Mistake 4: Not Considering Service Deprecation

Mike’s suggestion emphasized the importance of considering service deprecation when designing Azure solutions. He shared an example of Azure AD B2C being deprecated and the need to migrate to a new service. The lesson learned is to always check the lifecycle of a service and plan for potential deprecations.

Conclusion

Toon’s final message emphasized the importance of investing in Azure governance, including identity, network security, naming conventions, and DevOps. He encouraged organizations to prioritize governance to ensure a solid foundation for their Azure solutions.