I followed the documentation on https://support.office.com/en-ie/article/Deploy-Office-Add-ins-in-the-Office-365-Admin-Center-737e8c86-be63-44d7-bf02-492fa7cd9c3f to publish a created addin to our users. Unfortunately it is not showing up when users check out their Add Inns ( I see a caption Office 365 / Managed by admin but no selectable addin.
I tried:
Restarted MS Word
Logging in and out from MS Word does not help.
Removing the add in and adding again (through file or URL both not work)
Any ideas?
We seem to have the same issue; If you intercept the HTTPS traffic (by Fiddler for instance), do you see a 500 response to the 'POST /ews/exchange.asmx' with the body containing 'GetPrivateCatalogAddIns'?
So far, this seems to be an issue with Exchange internals. We've been trying to get into contact with Microsoft about the issue. Here you can find the StackOverflow issue we have filed, and Here you can find the question on the MS fora.
EDIT: It was confirmed that this was indeed an internal problem. We have removed our deployed plug-ins and added them again. The call now responds with a 200 and everything seems to be working again.
Unfortunately, we also found out that there is an issue with the Add-in registration interface in the Office 365 Admin Centre, as people who are not full administrator but User management administrator instead can no longer upload Add-ins due to an Exchange credential error. A Office 365 Administrator however can and this seems to be working with us.
Today I had a support engineer of Microsoft on the phone about my case and they resolved the issue. I can deploy add-ins again.
Related
I am using my email and password to send email using python script. But I am not able to send mail since past couple of weeks.
I debugged and found error.
Msg: b"Your message wasn't delivered because your client settings need to be updated to Microsoft Exchange. For more info see https://x.co/client"
on windows machine using outlook I also updated my email to Microsoft Exchange but still my problem is not resolved.
Can someone guide me on this?
Note: From outlook web and app email send/receive both are working fine. problem is only with script smtp.
Main Purpose is to use same details with flask-mail in flask project.
MAIL_SERVER="smtpout.secureserver.net"
MAIL_PORT=465
MAIL_USE_SSL=1
MAIL_USERNAME="______________"
MAIL_PASSWORD="______________"
I have an Outlook Web Addin, running in O365. This is currently hosted at my first server. (oldserver.domain.com)
I wanted to change the address the addin calls, so I changed all Urls in the Manifest file to (newserver.domain.com)and uploded it via the Microsoft 356 Admin Center. The new manifest was accepted, but the Addin is always calling the oldserver.domain.com. Since these updates sometime take a while to finish, I waited for the next morning.
I found this:
How often does the Outlook exchange server pull the web-addin manifest if they are "sideload" installed via URL
With this description it should already work. How can I get my addin to call the new url?
The changes may take an effect in up to 24 hours, not just next morning. You can find the following statement in the Deploy add-ins in the admin center article:
Outlook add-ins can take up to 24 hours to appear on app ribbons.
Sometimes it is necessary to enable and disable the add-in (multiple times) from the Office 365 admin center.
Our Global company is in the process of rolling out office 365 for the whole group. currently i am the only user in my location to start using office 365. I can create a new outlook 2013 profile for the office 365 account and it works well. Problem i'm having is after launching the new Office 365 profile outlook keeps prompting me for my local windows username and password. this only happens when i'm connecting to my local network. Our local exchange server is still in production and cant be removed at this stage as all my other 400+ users use it.
If i connect to my office 365 profile in outlook from another network this does not happen.
I created a new profile for outlook 2013 and this still occurs.
If i enter my credentials in outlook 2013 it downloads my local OAB instead of using the new Office 365 address book.
Current setup: Local Exchange 2007 server.
Office 2013 on windows 7 64bit
Microsoft employee here - sorry to hear about the difficulties you're having!
Can you answer these questions for me:
1. What specific Outlook 2013 version are you using? e.g. 15.0.4631.1000
2. Does the problem still occur if you set the ExcludeScpLookup Autodiscover reg value? Steps to do so can be found below:
a. Start regedit
b. Select reg key HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoDiscover
c. Create a new DWORD value in this AutoDiscover reg key named "ExcludeScpLookup" (no quotes) with value 1
d. Restart Outlook and boot into your O365 profile
Note that #2 is not a permanent solution, just a troubleshooting step to determine where the issue might be occurring. Please delete that reg value after confirming whether or not the issue still occurs with it set.
Thanks!
I have a problem with an emailing.
I am testing on 2 different PCs, same OS, same version Outlook (2007). But for my email, I haven't same result for each Outlook...
How is it possible ? How can I have different results with the same config?
Is one account through a work server? I had this issue with a corporate MS Exchange server removing some of the CSS from the tag (probably for security).
hope somebody can help me as I'm banging my head against the wall with this one! I've read and researched as best I can but cannot find a solution.
I have an Exchange 2010 server. The active directory domain is example.com and all my users are like this: first.last#example.com.
However, I've set the URL in IIS for Outlook Web Access to https://exchange.example.net. (Notice it's a .NET tld), because I have site-wide SSL certificate for *.example.net.
This is my desired set up. It works great.
However, Autodiscover is causing me a problem in Outlook 2010 clients. About 30 seconds after opening outlook and after the connection to Exchange is established (successfully), I get a certificate warning telling me the certificate name does not match.
It pops up twice, first for autodiscover.example.com and then exchange.example.com.
I need to change the URLs to autodiscover.example.NET and exchange.example.NET.
PLEASE can somebody help me - it's driving me to despair!
Thanks,
Simon.
Open a ExchangeManagmentShell (Powershell with Exchange Extension) and issue this command:
Get-ExchangeCertificate |select -ExpandProperty CertificateDomains
Can you see your domainname in the output?