Working in IT for more than two decades I was witness different situations when an IT System was in great danger. Application implementation, running environment, business requirements for application availability have influence on how the application should be protected in case of unpredictable circumstances.
During my IT experience I implemented numerous IT projects with different requirements regarding the requirements for High Availability and Disaster Recovery. Reporting System in intranet is for sure important but steering of power stations has higher importance, as well as IT Systems (for example) in health care. Even in banking area different systems requires different levels of attention during the disaster.
Alexander Sosedko, Dr. Stefan Malich, Maik Schwill: Large Scale Adoption of Azure. Azure Meetup Ruhrgebiet, No. 23, November, 2019.
A man with healthy lifestyle has higher resistance against illness compared to unhealthy one.
So properly architected software is the basics for "healthy life" of the product, it leads to reduction in dependencies and cost.
According to my experience working in different roles in IT, I have very often touch points with the topic of "vendor lock-in". This topic is quiet often discussed and is part of various concepts and processes. Sometimes to avoid vendor lock-in is a goal within vendor management, strategy, and operations departments. Some architects used it as part of assessment processes and thus incorporate into architectural principles like: "Avoid Vendor lock-in…".