Are you testing component resources? The preferred solution here is to not test the Azure SDK: it's already tested by Microsoft. If you have the calls to the SDK outside your component resources, and pass the resulting objects / values into the component resources' constructors, then this problem goes away.
little-cartoon-10569
09/21/2022, 8:10 PM
Bringing a functional approach to components makes testing a lot easier.
g
gorgeous-accountant-60580
09/22/2022, 6:03 PM
Thanks for the feedback, @little-cartoon-10569. This was indeed the right way to go