Is there any API to create email audit monitor in outlook? - outlook-addin

G-Suite has an email audit api where admin can create an audit monitor on the source user. All the emails TO and FROM source user will be forwarded to destination user in MIME format. Does outlook also have any such API's to audit emails? I went through the documentation and looks like it's just audit logs but not email forwarding. I am pretty new to outlook and this feature is very critical to developing our Add-in.
Any help around this is greatly appreciated.

Currently the feature you requested, is not a part of the product. We track Outlook add-in feature requests on our user voice page . Please add your request there. Feature requests on user-voice are considered when we go through our planning process.

Related

How do I hide an Outlook JS Add-In for OWA, but not for other applications (desktop outlook, Office365)?

Is there an option in the manifest.xml to stop the Add-In from appearing in the OWA app ?
It appears that FormSettings is a mandatory field, and at least one Form is required.
There are some functional parity issues with OWA (e.g. UI-less action, TaskPane for EditItems) that push us to forego having it there.
Thanks!
Currently the feature : "showing add-in on specific platform"
, you requested, is not a part of the product. We track Outlook add-in feature requests on our user-voice page. Please add your request there. Feature requests on user-voice are considered, when we go through our planning process.
There are no options currently. You may post your feedback or request on the UserVoice page.

I find no way to set the visibility of the GSuite Marketplace API to PUBLIC

When I try to publish my app on the Gsuite Marketplace via GCP, I find no way to change the setting 'Visibility'. Event if the app has never been published.
Between the two options (My Domain - Public), My domain is selected and can't be switched to Public, so nobody has access to my app.
Any help?
I've tried to contact the support and find help on forums but no answer at all.
First step, I'd recommend reviewing Choosing where to publish to ensure that you've published to the correct location. As noted under Publish your app (before you publish), your app is reviewed to determine if it meets the requirements for the relevant store. Additionally, your application may also have to undergo OAuth verification (I think this could be the problem) , and security assessment if it accesses user data, such as Gmail, Drive, Contacts, or Calendar
If your app is exempt from verification or if you've already undergone assessment and been approved, and your issue persists, I'd recommend contacting Marketplace Developer Support, via the below steps, who can assist you with your publishing issue.
Navigate to the new Developer Dashboard.
Click Contact Us.
The Developer Support contact us form is displayed.
I've tried to contact the support and find help on forums but no answer at all.
How did you contact Google Support? They have many teams and sometimes agents are not aware of the scope of support. Personally I would contact GCP Support first to verify your App in GCP, once they confirm everything is working from their end they need to route the case to GSuite with an Admin Console specialist to debug the problem

Cannot message bot due to 'Your administrator prevented you from talking to bots in direct messages'

We have a simple hangouts bot that has been working fine for several months. Starting yesterday 1 or 2 users indicated that they were receiving an error message when talking to the bot indicating that: 'Your administrator prevented you from talking to bots in direct messages'. Over the past 24-hours more and more people reported that the issue started happening to them until it was everyone. When it happened to me earlier today I messaged the bot 2 times about 5-minutes apart, it worked the first time then the second time I got the administrator prevented message.
I tested the #meet and #drive bot's and they both still appear to work.
I have confirmed that none of the settings on the bot have changed, most importantly that the 'Bot works in direct messages' option is still checked.
I have talked to our IT administrator who says that no settings have changed in our GSuite setup.
Looking through the documentation I can't find any mention of an issue or setting that would cause the above error. Is anyone aware of what could be causing the above.
Google Support statement
(...) if your domain currently applies a whitelist to restrict the set of G Suite Marketplace apps that users can install, existing internal bots may stop working. In order to appear and continue to function for users, the developers of these bots need to publish the bots to the domain as you can see on link. (...)
Solution
As said Jordansan this issue is related to the domain administration and to security enhancements. You may still use up to 5 email addresses to do your tests. Once you want your bot public, you will need to list it on the G Suite Marketplace.
To do so follow this guide Listing your bot on G Suite Marketplace. An extract is provided below :
G Suite Marketplace publication steps
This section tells you the specific steps you need to perform to publish your bot on G Suite Marketplace. The general steps are:
Create an OAuth client ID, if your project doesn't already have one.
Add the G Suite Marketplace SDK to your project and populate its configuration tab.
Populate the SDK's publish tab and submit.
The detailed steps for each of these are described in the following paragraphs.
For security reasons most organizations have (and should have) whitelisting enabled, which will prevent non white-listed marketplace apps to be enabled within the organization.
To deploy your bot you'll need to contact your GCP responsible and ask him to whitelist your bot.
Temporary solutions
What you can do is make the bot accessible to everyone in your organization. Assuming that the bot can be published.
If the bot shouldn't be public, you may implement your own connector to filter incoming queries and allow only selected email addresses. However the bot will still appear to everyone on the search screen, and everyone will be able to message it.
It's possible that your domain makes use of a new feature which requires bots to be whitelisted. This was introduced in a recent update. Previously, the admin setting was binary in that you could allow either all bots or none. Now any second party bots must be whitelisted if the administrator settings for that domain requires whitelisting.
You can find more information here: https://support.google.com/a/answer/6089179
I opened a ticket here: https://issuetracker.google.com/issues/137266964
Edit: We got this working by following the steps listed here: https://developers.google.com/hangouts/chat/how-tos/gsm-list and our GSuite admin white-listed the Bot for internal use. This eliminates the 5 user limitation and keep the current security settings in place for all other bots & GSuite Applications

Office Add-in + Auth0 - Trouble with keeping users logged in

Background
I'm developing an Office Add-in for Outlook. I'm using Auth0 for authenticating users before the client can access my API. So far I'm only allowing users to log in using the username / password connection (no social login).
I'm having an issue with users having to log in quite often.
What I've tried
I've tried to following approaches and failed:
Refresh tokens - not allowed due to the browser context
Silent auth - seems like it's not working that well (sessions are terminated frequently)
Questions
Why does the session terminate so frequently (disabling silent auth)?
What decides if the session is terminated at all?
Would it help to use Microsoft social login?
I'm happy to read any relevant material - I'm just not sure where to look. So please reference any material that can be helpful.
If Azure active directory is your Auth provider/ gating access to your API and the user is an O365 user then you can use Single Sign on for office. The capability is currently in preview and will be released soon.
https://learn.microsoft.com/en-us/outlook/add-ins/implement-sso-in-outlook-add-in
You still need to implement oAuth flow if your add-in is going to be used on outlook mobile or exchange on-prem. In that case after the user complete the oatuh flow. You need to keep a mapping of the exchange identity token and access/ refresh token on your end.
The article linked above explains that as well.

Best API for syncing Exchange Email/Calendar to my webapp?

Looking for additional products similar to www.nylas.com which provide an API to sync my web application with my microsoft exchange email and calendar.
Most email services are aimed at marketing and hosting, whereas I just want a simple connection between exchange and my app, without building an API from the ground up.
Any suggestions?
Why not using Exchange EWS?
Calendars and EWS in Exchange
Working with calendar items by using the EWS Managed API 2.0
I do not know your App so a simple cronjob would do it...
P.S.
By the way I personally think the best way is to access the calendar via the App directly on the device. The reason is that a user normally have ActiveSync configured so that he get all the content on his device. If he change his password he do that on the device. So your app might use a old password and will no longer work. Additional your app try to access content with the old password and might block the user account then. The user got upset and will no longer use it. Accessing the calendar now directly on the device eliminate the need to get the user password and also eleminite the need that the user need to change it in your app...