Forum Widgets
Latest Discussions
Shared Mailbox can have a password and login enabled without license
I'm very much aware of the license requirements for Shared Mailboxes in Exchange Online and for all Shared Mailboxes we always give licensed users access to them. If we need to login to the actual shared mailbox, we assigned them a license. This could be necessary if you also have some 3rd party application that actually need to login to the mailbox and fetch e-mail for some reason. I have recently realized that you CAN actually set a password to a Shared Mailbox. Just go to admin.microsoft.com > Users > Active Users > select the Shared Mailbox > Reset password. After this, you can login with the username/password. Of course, if you access it via portal.office.com you won't see Outlook but if you go directly to outlook.office365.com you will get access to the mailbox. Anyone know anything more about this feature? Limitations? I'm not looking to break the licensing terms, all our physical users for all our customers have their own personal accounts but there are scenarios where you have a 3rd party application accessing the mailbox for some reason.Exchange Server error in '/owa' application
ASSERT: HMACProvider.GetCertificates:protectionCertificates.Length<1 Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: Microsoft.Exchange.Diagnostics.ExAssertException: ASSERT: HMACProvider.GetCertificates:protectionCertificates.Length<1 Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [ExAssertException: ASSERT: HMACProvider.GetCertificates:protectionCertificates.Length<1] Microsoft.Exchange.Diagnostics.ExAssert.AssertInternal(String formatString, Object[] parameters) +241 Microsoft.Exchange.Clients.Common.HmacProvider.GetCertificates() +478 Microsoft.Exchange.Clients.Common.HmacProvider.GetHmacProvider() +143 Microsoft.Exchange.Clients.Common.HmacProvider.ComputeHmac(Byte[][] messageArrays) +16 Microsoft.Exchange.HttpProxy.FbaModule.SetCadataCookies(HttpApplication httpApplication) +826 Microsoft.Exchange.HttpProxy.FbaFormPostProxyRequestHandler.HandleFbaFormPost(BackEndServer backEndServer) +2776 Microsoft.Exchange.HttpProxy.FbaFormPostProxyRequestHandler.ShouldContinueProxy() +20 Microsoft.Exchange.HttpProxy.ProxyRequestHandler.BeginProxyRequestOrRecalculate() +229 Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon beacon) +1379 Microsoft.Exchange.HttpProxy.<>c__DisplayClass3f.<OnCalculateTargetBackEndCompleted>b__3e() +311 Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate) +35 Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate, LastChanceExceptionHandler exceptionHandler) +121 Microsoft.Exchange.HttpProxy.ProxyRequestHandler.CallThreadEntranceMethod(MethodDelegate method) +69 [AggregateException: One or more errors occurred.] Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result) +416 System.Web.CallHandlerExecutionStep.InvokeEndHandler(IAsyncResult ar) +231 System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +172
Rule using wildcard (or domain) for handling incoming emails
In line with the email security best practices recommended at Ignite this year, we are blocking our staff from using auto-forwarding rules in Outlook/Exchange Online. However there are valid scenarios where they need to know certain urgent emails have been delivered. We have many staff working for clients or partner companies in sensitive industries where they are not permitted to access Office 365 (or indeed any webmail service) while at work. What I want them to be able to do on their Office 365 email, account is something like: IF sender = *@importantclient.com THEN send notification to myemail@importantclient.com There are variations (perhaps include the subject line or from address in the notification, butt not the content), but that is the general idea. I can do it for fixed email addresses such as knownaccount@importantclient.com, but can't find any way for end users to do this for domains (@importantclient.com or *@importantclient.com) or other wildcards (from:managersname@*). I've tried in Outlook and Flow, but can't seem to make it work. I know it is possible with a Transport Rule, but I don't feel inclined to give my end user enough access to create these, for some strange reason.. Is this doable in O365 in any way (Outlook, Exchange, Flow, anything) in a way that normal (non-technical) users are likely to be able to handle? Thanks, Bob.
"NeedsApproval"
Hi All, So I have been migrating mailboxes from onprem to O365 in the hybrid config with no issues. Today I have two migration batch jobs that state "NeedsApproval", but everything migrated. Kind of confused as i don't see a way to "approve" the jobs and I don't see any issues. Any ideas?Outlook - Certificate has been revoked
Hi all, not sure if anyone has experienced it, but we are getting tthis error multiple times a day when using outlook. It says : Outlook.office365.com Information you Exchange with this site cannot be viewed or changed by others. However, there is a problem with the sites security certificate. The security certificate for this site has been revoked, This site should not be trusted, If we dont click OK, outlook cannot send or receive emails. Sometime this window is hidden behind and therefor are not aware of it during the day. if we click view certificate, it looks legit and everything seems to be ok. If enter OWA, we get same certificate(according to thumbprint), but there is no warning or error, We have created a case with Exchange online team, but they say there are no error from their side and its internal network issue. We have cleared certificate revoke list from our DNS servers without any help. Any ideas on how to troubleshoot this further? We use Outlook 2016 with latest updates and have all mailboxes in Exchange online. I only have my archive mailbox attached to my outlook, Thanks!Updating SSL Certificate
Hello! I am trying to update our expiring SSL certificate and here is what I am following to do so: To Install an Intermediate Certificate in Microsoft Exchange Server 2016 ClickStart, and then clickRun.... Typemmc, and then clickOK. The Microsoft Management Console (Console1) window opens. In theConsole1window, clickFile, and then selectAdd/Remove Snap-in. In theAdd or Remove Snap-inswindow, selectCertificates, and then clickAdd. In theComputer Accountwindow, selectComputer Account, and then clickNext. In theSelect Computerwindow, selectLocal Computer, and then clickFinish. In theAdd or Remove Snap-inswindow, clickOK. In theConsole1window, click+to expand theCertificates (Local Computer)folder on the left. Right-clickIntermediate Certification Authorities, mouse overAll Tasks, and then clickImport. In theCertificate Import Wizardwindow, clickNext. ClickBrowseto find the intermediate certificate file. In theOpenwindow, change the file extension filter toPKCS #7 Certificates (*.spc;*.p7b), select the*_iis_intermediates.p7bfile, and then clickOpen. In theCertificate Import Wizardwindow, clickNext. SelectPlace all certificates in the following store, and then clickBrowse. In theSelect Certificate Storewindow, selectIntermediate Certification Authorities, and then clickOK. In theCertificate Import Wizardwindow, clickNext. ClickFinish. ClickOK. Close theConsole1window, and then clickNoto remove the console settings. To Install an SSL Certificate in Microsoft Exchange Server 2016 Log in to theExchange Admin Center. From the left menu, selectServers, and then clickCertificates. Select your certificate (it has a “Pending request” status), and then clickComplete. ForFile to import from, enter the certificate file path we provided (such as\\server\folder\coolexample.crt), and then clickOK. Exchange installs your certificate. In theCertificatessection, select your certificate again (the status changed to “Valid”), and then clickEdit(pencil icon). ClickServices, select the services to which the certificate applies (SMTP, UM, UM call router, IMAP, POP, and/or IIS), and then clickOK. Your certificate is now ready to use with Exchange 2016. The issue I get is at the "pending certificate" does not show up in the list in EAS, just the original certificate still showing "expires on" as shown in the image. I have tried several times, verified that I am downloading the Exchange SLL, verified that it is for this particular server, restarted IIS etc etc. The server is on prem physical Windows 2016 Exchange server and there is only only one. Ideas? Thanks!
