How to Simulate Fallback for Unsupported Nested App Authentication in Outlook Add-in?

Diksha Yadav 101 Reputation points
2025-04-21T11:37:01.7333333+00:00

I'm currently implementing Nested App Authentication for an Outlook Add-in, and the authentication flow is working as expected when supported.

However, I need to test the fallback mechanism that should trigger when Nested App Authentication is not supportedby the host Outlook client.

Is there a recommended way to simulate or force this unsupported scenario for testing purposes—either via configuration, environment, or specific client versions?

Any guidance or workaround to validate the fallback logic would be greatly appreciated.

Office Development
Office Development
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Development: The process of researching, productizing, and refining new or existing technologies.
4,344 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Hien-L 900 Reputation points Microsoft External Staff
    2025-04-22T07:55:01.42+00:00

    Hi Diksha Yadav,

    Welcome to our forum!

    It seems your case is more related to Outlook add-in development, please kindly understand that the Outlook tag here we mainly focus on general issues about Outlook desktop client. It's suggested that you could post your case in dedicated tag for development for more professional advice: Office Development.

    Thanks for your support and understanding.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.