Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outlook Web Add-In Presents Domain Trust Dialog to Users in On-Exchange premises 2019 OWA #4055

Open
avisheknand opened this issue Jan 25, 2024 · 4 comments
Assignees
Labels
Area: Outlook Issue related to Outlook add-ins Resolution: by design Issue is by design

Comments

@avisheknand
Copy link

We have an Outlook web add-in that implements the OnSend event deployed via Admin center centralized deployment that is presenting users with the following prompt:

image

image

Your Environment

  • Platform [PC desktop, Mac, iOS, Office on the web]: OWA
  • Host [Excel, Word, PowerPoint, etc.]: Outlook
  • Office version number: Exchange on premises 2019 OWA
  • Operating System: Windows 10 (21H2)
  • Browser (if using Office on the web): Edge

Expected behavior

I'm expecting to be able to, as the tenant/global admin, to be able to trust the add-in (Similar to how global admins grant consent to apps to avoid users faced with consent prompts) such that users aren't presented with the prompt. Is this possible?

Also able to make the OnSend Addin work without the any issue

Current behavior

Instead of experiencing the anticipated functionality outlined earlier, users encounter prompts as described in the summary above. These prompts create an impression that the add-in may not be secure, despite having undergone thorough vetting by administrators.

Steps to reproduce

1.The prompt appears when after hitting send on a message.

Link to live example(s)

  1. Unfortunately, I'm not able to provide a live example publicly.

Context

My customer is trying to enforce compliance on messages as they are being sent, so it's imperative that we're able to leverage an OnSend event add-in.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP label Jan 25, 2024
@exextoc exextoc added Needs: attention 👋 Waiting on Microsoft to provide feedback Area: Outlook Issue related to Outlook add-ins and removed Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP labels Jan 25, 2024
@exextoc exextoc self-assigned this Jan 25, 2024
@avisheknand
Copy link
Author

Hello any help or guide on this would be appreciated

@exextoc
Copy link
Collaborator

exextoc commented Jan 29, 2024

The behavior is by design.

Please find the doc around it here : Description of the security update for Microsoft Exchange Server 2019, 2016, and 2013: October 13, 2020 - Microsoft Support

@exextoc exextoc added Resolution: by design Issue is by design and removed Needs: attention 👋 Waiting on Microsoft to provide feedback labels Jan 29, 2024
@ajays-msft
Copy link

ajays-msft commented Jan 30, 2024

Similar issue #3310 which is closed as by design.

@avisheknand
Copy link
Author

Thanks @exextoc and @ajays-msft , we have informed the customer and they are able to use the addin now by adding the domain to the browsers cookie

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Outlook Issue related to Outlook add-ins Resolution: by design Issue is by design
Projects
None yet
Development

No branches or pull requests

3 participants