We cannot launch our examples with with on-send feature for OWA in Office365.
Enabling the on send feature
By default, on send functionality is disabled. Administrators can enable on send by running Exchange Online PowerShell cmdlets.
How can we enable this feature for our developer account in Office365 for testing purposes.
Thanks.
This describes how to enable on send. https://learn.microsoft.com/en-us/outlook/add-ins/outlook-on-send-addins#enabling-the-on-send-feature
The section "Enabling the on send feature" includes the commands you need to run. Information on Exchange Online Powershell: https://technet.microsoft.com/en-us/library/jj984289(v=exchg.160).aspx
Related
Something I can't seem to wrap my head around:
Enabled CA for Exchange Online and Sharepoint online to be accesible only from Intune compliant devices, works great.
On my iPhone I downloaded the Sharepoint app, logged in, and that works great. Same for the Onedrive app.
But when I try access either Sharepoint or Onedrive from another app (PDF-Expert to edit PDF's), it gives an error message:
Login failed, please try again later.
When I look at the user sign-ins, I see a successful login from the PDF-exert app, and when I turn off CA for Sharepoint online, I can successfully add both the Onedrive and Sharepoint source in the PDF-expert app. I've experimented with the "client apps" and selected everything and nothing, but that makes no difference.
Any ideas where to look further?
Here is a picture of my configured CA.
Note: currently it's one user who uses this, but exempting that user from CA beats the purpose of having CA, so that's not an option.
After contact with support and the support team from the PDF-Expert app we discovered that the issue lies with the app.
As far as we've understood from your logs, your OneDrive account requires MDM support which is not available in PDF Expert app. Our developers already aware of the issue with such accounts so they'll consider adding OneDrive MDM support in the future versions of PDF Expert app.
Now we wait until they make an update to support this.
I had configured an Incoming Webhook on one of our Microsoft Teams channels, but noticed it stopped working recently, and also I am no longer able to find the Incoming Webhook in the list of connectors:
What command would I need to have our Administrators run or what configuration would I need to apply to get this to work again?
As #wajeed-msft notes, this is happening because your administrator turned off access to external applications.
Assuming "Allow sideloading of external apps" is also turned off you'll get the list on the page you found above. If you scroll through that list, you will see "Incoming webhook" listed.
I had the same problem and I didn't remember that I (as a Tenant admin) disabled anything in the portal. "Unfortunatly" the screenshot is from the older portal, in the new Teams Admin check the following:
All available connectors were somehow blocked, so I removed everything from the "blocked apps" list:
Then I needed to sign out ("Quit" didn't refresh those settings) and sign in again and now I have access to all connectors.
For webhook connector, you can use the incoming webhook connector in MS teams app sections.
For more information please refer this link
I am trying to add a docusign connect listener but when I click on switch to classic application, it takes me back to new application landing page. I have a professional account. Please tell me if I am doing anything wrong?
You need to use your free developer sandbox account to test DocuSign Connect, not your paid production account. If you do an API Integration that uses Connect and you want to enable in production environment then you need go through DocuSign's API Certification Process. Login to your dev account and the switch back to Classic will work.
To create a free dev sandbox check out the home page:
https://www.docusign.com/developer-center
And see the Go Live section for information regarding API Certification: https://www.docusign.com/developer-center/go-live/overview
I have deployed Orchard on azure and enable Email Messaging module. Enabling says it enables successfully and asks for email settings. I provided it the mail server setting. Strange thing is, User setting does not show me the settings which are dependent on email messaging module (Contact us email address and public site name) and does not show me ("Lost your password") link . Also I have built a module which sends email. This module is not sending email.
Same orchard package works fine and also email on my dev server with same mail server settngs(gmail smtp settings.) But email is not working on azure.
What am i Missing ?
thanx
Just FYI for anyone else who visits this Question, I just got this working from Azure using the gmail SMTP server without any third party add-ons. I simply added the following SMTP details:
Then used the contact form to send an email to myself. The first email gives me an alert to my gmail account:
Hi Simon,
Someone recently tried to use an application to sign in to your Google Account - XXX#gmail.com.
We prevented the sign-in attempt in case this was a hijacker trying to access your account. Please review the details of the sign-in attempt:
Monday, April 8, 2013 9:33:46 PM UTC
IP Address: 65.52.168.70
Location: United States
...blah blah blah
If this was you, and you are having trouble accessing your account, complete the troubleshooting steps listed at http://support.google.com/mail?p=client_login
Following the link give you the option to allow an application to login with your credentials. Just follow the link in step 3 and then you have 10 minutes to send another email from your orchard site. The next test message I received without issue.
Got it. Windows Azure itself does not allow sending email neither it allows to use SMTP. WE have to use third party email service like PostMark,SendGrid etc
http://blogs.msdn.com/b/publicsector/archive/2011/10/14/sending-and-receiving-email-in-windows-azure.aspx
So, I'm just curious how does WordPress, installed on Windows Azure (gallery), able to send emails?
http://coffee2code.com/wp-plugins/configure-smtp/
There are still too many different suggestions on the subject so i thought i should write what I've found useful. Here's what i did to get it to work:
My SMTP settings:
Sender address: myname#gmail.com
Hostname: smtp#gmail.com
Port: 587 (25 will also do)
SSL Communications: Checked
Credentials: My Gmail address and my password
These settings should work on your local environment just fine. But on the cloud you may need to do the following:
As your Azure VM may be at some arbitrary location, Gmail marks the login attempts as suspicious and blocks them. If this is the case, you should see a mail informing you about this suspicious activity in your inbox. Just follow the instructions there and mark the login as trusted. It will remain that way until somehow your IP on the cloud changes (e.g. deleting your deployment slot). VM relocation shouldn't be an issue since the IP still remains the same. You may have to do this separately for your staging and production slots.
Lastly, I enabled full trust for my web role as shown here:
http://blogs.msdn.com/b/windowsazure/archive/2009/03/18/hosting-roles-under-net-full-trust.aspx
I hope this helps others having this problem.
Cheers
No more third-party with GitLab 15.5 (October 2022):
Deliver emails using Microsoft Graph API with client credentials flow
If you’ve enabled security defaults in Azure AD,
legacy authentication protocols for SMTP are blocked.
You can now configure your GitLab instance to deliver emails using
Microsoft Graph API
with OAuth 2.0 client credentials flow.
See Epic, Documentation and Merge Request.
The gitlab.rb would include:
gitlab_rails['microsoft_graph_mailer_enabled'] = true
# The unique identifier for the user. To use Microsoft Graph on behalf of the user.
gitlab_rails['microsoft_graph_mailer_user_id'] = "YOUR_USER_ID"
# The directory tenant the application plans to operate against, in GUID or domain-name format.
gitlab_rails['microsoft_graph_mailer_tenant'] = "YOUR_TENANT_ID"
# The application ID that's assigned to your app. You can find this information in the portal where you registered your app.
gitlab_rails['microsoft_graph_mailer_client_id'] = "YOUR_CLIENT_ID"
# The client secret that you generated for your app in the app registration portal.
gitlab_rails['microsoft_graph_mailer_client_secret'] = "YOUR_CLIENT_SECRET_ID"
gitlab_rails['microsoft_graph_mailer_azure_ad_endpoint'] = "https://login.microsoftonline.com"
gitlab_rails['microsoft_graph_mailer_graph_endpoint'] = "https://graph.microsoft.com"
I am running MOSS 2007 on a Windows 2003 box. I need to know what configuration must be done to get Alerts to work. SMTP settings, etc.... When I create my alert, it is created but it does not send the email to show me that something changed in my document library or on any particular document. What am I missing?
I did install the Email Services under Windows Components and the SMTP under IIS.
In my SharePoint Central Admin, I did change my settings for outgoing and incoming email (Under the Topology and Services section).
What else am I missing?
Did you setup the Web Application Outgoing E-mail Settings in your Central Administration? Y
Has the SMTP server been configured to allow the MOSS server to relay mail to it?
Ensure that you have configured the SMTP server properly by configuring an account and associating to a mail client Outlook. Check the Servers outgoing and incoming capabilites from the mail client first.
Ensure that you have subscribed to the alerts properly in a list
I don't think this question is really appropriate for StackOverflow - its not a programming question, see the FAQ.
But anyway - could be anti-virus or smtp relay rules stopping sharepoint sending smtp to your mail server. Try this tool to diagnose.
http://www.simplecomtools.com/smtptesttool.html
If that doesn't work then its MS support - the newsgroups are littered with the carcasses of people trying to resolve alert email problems!