An architecture exception process is a mechanism to handle requests for deviations from the established IT architecture policies or standards. It allows the enterprise to evaluate the business case, risks, benefits, and alternatives of implementing a system that uses a technology that is not in line with its IT strategy. It also enables the enterprise to define the conditions, limitations, and timelines for granting or denying the exception. According to one of the web search results1, "requests for exceptions to any architectural policy or standard use this process" and "the decision may include a deadline for removing the need for the exception, constraints on future projects, or similar terms." Addressing the situation as part of an architecture exception process is the best way to manage it within an IT governance framework, as it provides a structured and transparent way to balance the business needs and the IT alignment. Updating the IT strategy to align with the new technology, initiating an operational change request, or rejecting based on non-alignment are not the best ways to manage the situation within an IT governance framework. They are more likely to be either too rigid or too reactive, and may not consider the trade-offs or implications of the decision..
References:
CGEIT Review Manual 2021, Chapter 1: Governance of Enterprise IT, Section 1.4: Value Delivery, page 231 CGEIT Review Questions, Answers & Explanations Manual 2021, Question 9, page 82 A Matrixed Approach to Designing IT Governance - MIT Sloan Management Review3 Enterprise Architecture Governance | The Definitive Guide - LeanIX4 Architecture Review Board Exception Process - Minnesota's State Portal5