Recent 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.Solved711KViews3likes24CommentsExchange 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) +172Solved334KViews3likes56CommentsRule 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.312KViews0likes12CommentsShared mailbox: Use send-as, not send on behalf from Outlook 2016
Hello, We have a lot of shared mailboxes. For every shared mailbox, we create a specific security group that contains the members who should have access to that particular shared mailbox. We give full mailbox permissions and send-as permissions for that particular security group onto the shared mailbox. For example, security group A has full mailbox access and send-as permissions onto shared mailbox A. By adding users to security group A, they have full access to the shared mailbox. We create every new shared mailbox/security group combo using Powershell. That has been working flawlessly for the last years. However, for a recent new shared mailbox/security group combination, when a user that's member of the related security group wants to send an e-mail from the shared mailbox (by changing the from field in Outlook and selecting the shared mailbox from the global address list), Outlook tries to send every time 'send-on behalf'. This only happens for that newly created mailbox. I compared the output of Get-Mailbox and Get-RecipientPermission for the new problem shared mailbox and an older shared mailbox (which enable users to send mail send-as from outlook just fine) but I couldn't find any differences. For your information, that's the error we get back immediately after trying to do a send-as for the new shared mailbox: Your message did not reach some or all of the intended recipients. Subject: Test from Outlook Sent: 23/11/2017 9:27 The following recipient(s) cannot be reached: name of sending user on 23/11/2017 9:27 This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000524]. Why does Outlook always tries to do a send on behalf (what we don't want) where else for other shared mailboxes, send-as works fine? Using send-as from OWA however works just fine for the newest shared mailbox. It only seems a problem related to Outlook (tested on multiple clients that have access to the shared mailbox) and that particular new shared mailbox. Thanks in advance.Solved310KViews3likes12Comments"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?182KViews1like14CommentsOutlook - 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!147KViews1like40CommentsUpdating 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 Click Start, and then click Run.... Type mmc, and then click OK. The Microsoft Management Console (Console1) window opens. In the Console1 window, click File, and then select Add/Remove Snap-in. In the Add or Remove Snap-ins window, select Certificates, and then click Add. In the Computer Account window, select Computer Account, and then click Next. In the Select Computer window, select Local Computer, and then click Finish. In the Add or Remove Snap-ins window, click OK. In the Console1 window, click + to expand the Certificates (Local Computer) folder on the left. Right-click Intermediate Certification Authorities, mouse over All Tasks, and then click Import. In the Certificate Import Wizard window, click Next. Click Browse to find the intermediate certificate file. In the Open window, change the file extension filter to PKCS #7 Certificates (*.spc;*.p7b), select the *_iis_intermediates.p7b file, and then click Open. In the Certificate Import Wizard window, click Next. Select Place all certificates in the following store, and then click Browse. In the Select Certificate Store window, select Intermediate Certification Authorities, and then click OK. In the Certificate Import Wizard window, click Next. Click Finish. Click OK. Close the Console1 window, and then click No to remove the console settings. To Install an SSL Certificate in Microsoft Exchange Server 2016 Log in to the Exchange Admin Center. From the left menu, select Servers, and then click Certificates. Select your certificate (it has a “Pending request” status), and then click Complete. For File to import from, enter the certificate file path we provided (such as \\server\folder\coolexample.crt), and then click OK. Exchange installs your certificate. In the Certificates section, select your certificate again (the status changed to “Valid”), and then click Edit (pencil icon). Click Services, select the services to which the certificate applies (SMTP, UM, UM call router, IMAP, POP, and/or IIS), and then click OK. 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!120KViews0likes2CommentsAggregate availability from multiple calendars
I prefer to keep personal appointments on one calendar (on Outlook.com) and work appointments on my work calendar (O365 Exchange), but Exchange only seems to use my work calendar to show my availability to other people in my organization. I'd like to have a way to aggregate my availability from multiple calendar sources, the way that you can overlay multiple calendars in Outlook. It's not really a matter of me seeing all my appointments, because I can easily see everything in a consolidated view in Outlook on my desktop or mobile; it's more about letting others in my organization know when I'm free to meet. I know there is (used to be?) a "free/busy server" option in Outlook client, but I feel like this should be something that can be set on my Exchange profile, so that it doesn't matter what client I'm using. Aside from that kind of option, I guess I'd guess I might be OK with a solution that duplicates anything added to my personal calendar as a block on my work calendar or vice versa, even if it's an IFTTT-type thing. I saw a similar post that mentions some 3rd-party tools from CodeTwo and Connecting Software, but given this is just a preference of mine, I'm probably not going to spend a lot on a workaround. TLDR: Is there a better approach to showing consolidated availability than manually duplicating my appointments between calendars? Thanks!117KViews11likes30CommentsOutlook Meeting Updates Going Directly to Deleted Items
Microsoft made in change in how meeting updates are handled and smaller updates are now going directly to the Deleted items folder. This caused people to miss important updates to agenda items. I am wondering if other people also receive complaints about this? To me it seems strange that such a setting cannot be controlled by individual Outlook settings as there are settings for this already in place. Is Microsoft considering to allow this behavior to be controlled by the Outlook/Outlook on the web settings as an improvement over the current situation? Background information: Uservoice request: https://office365.uservoice.com/forums/325347-office-com-home-page/suggestions/37852648-ms-outlook-calendar-function-has-unwanted-autoproc Information about the change on the Microsoft roadmap: https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=meeting%2Cupdates Information about the settings to control this organization wide: https://docs.microsoft.com/en-us/powershell/module/exchange/organization/set-organizationconfig?view=exchange-ps Settings that can be set in Outlook and Outlook on the web that do not have any impact on this behavior: Outlook on the Web: Delete invitations and responses that have been updated Outlook: Automatically process meeting requests and responses to meeting requests and polls114KViews4likes15CommentsHow to Enable and Use Exchange Online’s External Email Tagging Feature
Exchange Online tenants can activate external email tagging, which causes Outlook clients (not desktop yet) to highlight messages received from external domains. The feature can replace custom implementations to mark external email, usually done with transport rules. It’s easy to implement and control, but the mail tip offering to block an external sender seems a little over the top. https://office365itpros.com/2021/03/11/exchange-online-external-email-tagging/111KViews0likes13CommentsUsing the Outlook Booking with Me Feature
Outlook’s new Booking with Me feature is rolling out worldwide. Any user with an Exchange Online license can create a personal bookings page to allow other internal and external people to book meetings with them. It’s a nice idea and a good example of how Microsoft can use its software toolkit to create new solutions. https://office365itpros.com/2022/07/25/booking-with-me/106KViews0likes5CommentsWhitelist Email Addresses/Domains for Certain Groups
What's the most effective way to manage email whitelists for certain groups of users (only)? Rather than whitelisting an email address or a domain for an entire tenant, how can we whitelist it for selected users and nobody else?103KViews0likes4CommentsHow can I make all users calendar shared with all other users?
How can I make the calendar for all users in a particular group shared with all other users in that group? And, any time I add a new user to the all staff group, their calendar is automatically shared? Thank you!97KViews0likes14Commentsdoes not designate permitted sender hosts
Hi Everyone I am hoping someone can assist me with the following issue. I have SPF and DKIM configured on my domain, which appear to be setup correctly but when I examine the message header of an email I sent I see the following entry "None (protection.outlook.com: za.cfao.com does not designate permitted sender hosts)" Just to add I am using Exclaimer for signature management. Please can someone examine the header below and advised if I configured something incorrectly. "Delivered-To: nsadheo@gmail.com Received: by 2002:a4f:c15:0:0:0:0:0 with SMTP id 21csp930979ivm; Wed, 21 Aug 2019 06:30:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqyk6Zvuz4Zzp1WUwoJQlz3EsF/mENO5B7uNOXkWXKiQUJ9CmIl25//eS3gDvDa/NqaFIZJg X-Received: by 2002:a17:906:158c:: with SMTP id k12mr31626198ejd.83.1566394255976; Wed, 21 Aug 2019 06:30:55 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1566394255; cv=pass; d=google.com; s=arc-20160816; b=lbJV6glrTA9esPnHzJRI/x2ugMmh1yM0zYOO4Hmhvpeuwblxjcnlf4yErbNS9ShdTC zz7tB3Tlp63d+mH95cXl0tVS6pXE852lUmxX47jdY5tuQ86Mn788xO/HP8y1VlFlamK2 zTuOJ3ow4d264I2lPWXgueWLQOOwVvjyLOsz0hxpo4TIfLY+YLvTr2XlDUW7F4ZIC50o fjfU5YP15UvEHg4+YPHRqmiMQyp6DT6No71nhWhbZyCdzTWFs6A8a2QJEYYuY5hccLd7 4sHcycJKruMu0BIGoa7e5O/BS5zXRxqoPzN9IvrMQu0IiI0hQS4Fc+iqTs+RRuRnl8Ex z3bA== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:content-language:accept-language:message-id:date :thread-index:thread-topic:subject:to:from:dkim-signature; bh=mEa8xeBYgC5oDAMvVia716t3ct7BI+dA6l0bklr8UAM=; b=AC+iiIgfhye53K/jD2GTMuQhsu1Us5iZQcxKe/x1ww59llPOzWCipIVOSJ6kO2/kM5 5QesFTIYMNlMRaJwaHWOkR+Muy2SRaaxpPhLc4lpbjmdZpgtxKZlyLmuXkx3UZvIVjzL hMOz4U7K6G0iDr8LgxsRRCjMWjUMBQAE6ohKsxlTT4aA1aiCp/Fqe48DjpBK8/Wwkj+5 Ui8Lvtv2xiwFIuRtITLmBNz0+Z2dbInt1pTAsMQhE5dJyH7TjIuFaPB484UNz3m21xX6 S1WKMEPP19uGuXCFJUtkSmZyJub93td7GsYXCE3v765FkYeTV7SukV6EQavzyE7esCLR OOtA== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@za.cfao.com header.s=selector2 header.b=FP6CtFnn; arc=pass (i=1 spf=pass spfdomain=za.cfao.com dkim=pass dkdomain=za.cfao.com dmarc=pass fromdomain=za.cfao.com); spf=pass (google.com: domain of nsadheo@za.cfao.com designates 40.107.5.95 as permitted sender) smtp.mailfrom=nsadheo@za.cfao.com Return-Path: <nsadheo@za.cfao.com> Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50095.outbound.protection.outlook.com. [40.107.5.95]) by mx.google.com with ESMTPS id p9si10358093ejf.115.2019.08.21.06.30.55 for <nsadheo@gmail.com> (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 21 Aug 2019 06:30:55 -0700 (PDT) Received-SPF: pass (google.com: domain of nsadheo@za.cfao.com designates 40.107.5.95 as permitted sender) client-ip=40.107.5.95; Authentication-Results: mx.google.com; dkim=pass header.i=@za.cfao.com header.s=selector2 header.b=FP6CtFnn; arc=pass (i=1 spf=pass spfdomain=za.cfao.com dkim=pass dkdomain=za.cfao.com dmarc=pass fromdomain=za.cfao.com); spf=pass (google.com: domain of nsadheo@za.cfao.com designates 40.107.5.95 as permitted sender) smtp.mailfrom=nsadheo@za.cfao.com ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=F+DwKETlHrzExLzhUmKe8DYH+g1ahFs/Ec9iuYU3WMOuPoD9LotwlIEWnRWr2ECk4a/jkV7N1x3bMakycJaZK/PYADiDo5GLXeaatvirya0YnMIYTNAV3rsmCKOxge1fkYTEi53IYOKBEy6kwAFnMEFlL9szBZ7JnUNyFu1tm17huZXUl4DT8nzAPcJs21gu5o2hGkKhPW7goMWDyZ/VVfQS7/q+X6uOwXStbGHhitkh2tw0Z6N7D4GPdU1WMxjrrmXYta4V2mGRvwM8K6s+QIEZx0h+2nmwvYQm9j5VeWQLsJ6HxWmVW4TDYBVbK7hjVk5l20iGZzpUnmndHc6Jjw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mEa8xeBYgC5oDAMvVia716t3ct7BI+dA6l0bklr8UAM=; b=OlIwiuD9XISvwzVd1HdhPWx6ADnQiHYi+SUnkn6XGlIYa0RLu27hdFJbPDupi6xFv/LFyXqjv+g2gGpsAWY5nVvIPqICsw6iF7kYot/oEmYlsyoabmZbY2kIQAqXrxOn0eLMv/V0/2saTO3KM0SuhWENDBfZ4HeJ3F8L6O7QqI5a+g0KMR5SxDeapiLVD/qTZ5RxFcyPHeysnw1o0j4fmtIPI8ZPAM8JYufhdO/AkWgsDC6N3JraMUvwVeE23tmYZBzruS6Ip51aiUuoeGMY3YBAhYnFlQgbPNXgy4WwRfxeCeLhoR7jzA1QXHrUNjY/qjMrYGtS4LsSw8eUWM2ewg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=za.cfao.com; dmarc=pass action=none header.from=za.cfao.com; dkim=pass header.d=za.cfao.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=za.cfao.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mEa8xeBYgC5oDAMvVia716t3ct7BI+dA6l0bklr8UAM=; b=FP6CtFnnw6NVQziPrjiZsfdDEBYGCCmQAq3O5/goannAvxIwiT8pJagAe9vqYgQOcn/OXY4lB0SqUmS5UfrZi/iumosCAUW8fd/dOm/ltG+4OyZ41zecTdTflhNvdiSgxEUldjLvURAnYgyFjxxCjzCMQEq7gVp/N8lAwZ2E7Rk= Received: from DB8P190MB0730.EURP190.PROD.OUTLOOK.COM (52.135.63.144) by DB8P190MB0730.EURP190.PROD.OUTLOOK.COM (52.135.63.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2178.16; Wed, 21 Aug 2019 13:30:54 +0000 Received: from DB8P190MB0730.EURP190.PROD.OUTLOOK.COM ([fe80::71bf:4419:8bc4:a699]) by DB8P190MB0730.EURP190.PROD.OUTLOOK.COM ([fe80::71bf:4419:8bc4:a699%2]) with mapi id 15.20.2178.020; Wed, 21 Aug 2019 13:30:54 +0000 From: Navishkar SADHEO <nsadheo@za.cfao.com> To: NC Sadheo <nsadheo@gmail.com> Subject: test1 Thread-Topic: test1 Thread-Index: AdVYJKY9mClFl38XRWend63MaL4MVg== Date: Wed, 21 Aug 2019 13:30:54 +0000 Message-ID: <DB8P190MB0730A5E666636DC0871F162FF1AA0@DB8P190MB0730.EURP190.PROD.OUTLOOK.COM> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=nsadheo@za.cfao.com; x-originating-ip: [105.23.225.190] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: cf0e2d89-8b6b-48db-e189-08d7263bcad7 x-microsoft-antispam: BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020);SRVR:DB8P190MB0730; x-ms-traffictypediagnostic: DB8P190MB0730: x-microsoft-antispam-prvs: <DB8P190MB0730D72F146971F54A573808F1AA0@DB8P190MB0730.EURP190.PROD.OUTLOOK.COM> x-ms-oob-tlc-oobclassifiers: OLM:1728; x-forefront-prvs: 0136C1DDA4 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(4636009)(346002)(396003)(376002)(366004)(136003)(39850400004)(199004)(189003)(81156014)(26005)(55016002)(6116002)(186003)(9686003)(3846002)(54896002)(6306002)(73894003)(74316002)(316002)(2906002)(102836004)(99286004)(6506007)(256004)(71190400001)(71200400001)(8936002)(33656002)(790700001)(7736002)(4270600006)(6436002)(25786009)(7116003)(6916009)(476003)(14454004)(486006)(76116006)(7696005)(66066001)(1411001)(66446008)(64756008)(66946007)(66476007)(66556008)(217283003)(52536014)(5660300002)(86362001)(8676002)(53936002)(81166006)(478600001);DIR:OUT;SFP:1102;SCL:1;SRVR:DB8P190MB0730;H:DB8P190MB0730.EURP190.PROD.OUTLOOK.COM;FPR:;SPF:None;LANG:en;PTR:InfoNoRecords;A:0;MX:1; received-spf: None (protection.outlook.com: za.cfao.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: s8HgQRDDo8xAYqnGArehkBX6oT8ql8aX1kVqtuMf+kHwheBv6i0An7xYGP7tvMkVskJljufiIPvSoWm7q166ekbNowo0HY2g0VptApLjHACVN+WRyRd1kXwfpT74x2BodJ2dS7BCsTzX6Ax1FZ1cq8FhDmRj8InG2vLlXes69Lgpwf8cHwbc578zHeALzuTHakLe7XlVZYLvL6/MQjLq+ARP1A7ybfgxvtMiJnk8keKAxOTB8+hblcaXjov0WsFtHvtKLr7fMLPlJUWOMYzMzoo383lWUX//97BLdB/tZbE= x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_DB8P190MB0730A5E666636DC0871F162FF1AA0DB8P190MB0730EURP_" MIME-Version: 1.0 X-OriginatorOrg: za.cfao.com X-MS-Exchange-CrossTenant-Network-Message-Id: cf0e2d89-8b6b-48db-e189-08d7263bcad7 X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Aug 2019 13:30:54.3575 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 15d1f070-0301-4099-9892-b8198001c1a6 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: ydoY64BQKqKLBzQBXy9uHHQqH1OTIdPN8oEyGwTG1DnCr2DEBjsc6ZYrkvgO8e/0qKNxTENPNdgObCvlqFC/YQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8P190MB0730 --_000_DB8P190MB0730A5E666636DC0871F162FF1AA0DB8P190MB0730EURP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable --_000_DB8P190MB0730A5E666636DC0871F162FF1AA0DB8P190MB0730EURP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face =09{font-family:"Cambria Math"; =09panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face =09{font-family:Calibri; =09panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face =09{font-family:"Segoe UI"; =09panose-1:2 11 5 2 4 2 4 2 2 3;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal =09{margin:0cm; =09margin-bottom:.0001pt; =09font-size:11.0pt; =09font-family:"Calibri",sans-serif; =09mso-fareast-language:EN-US;} a:link, span.MsoHyperlink =09{mso-style-priority:99; =09color:#0563C1; =09text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed =09{mso-style-priority:99; =09color:#954F72; =09text-decoration:underline;} span.EmailStyle17 =09{mso-style-type:personal-compose; =09font-family:"Segoe UI",sans-serif; =09color:windowtext;} .MsoChpDefault =09{mso-style-type:export-only; =09font-family:"Calibri",sans-serif; =09mso-fareast-language:EN-US;} @page WordSection1 =09{size:612.0pt 792.0pt; =09margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 =09{page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"EN-ZA" link=3D"#0563C1" vlink=3D"#954F72"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span style=3D"font-family:"Segoe UI",sans= -serif"><o:p> </o:p></span></p> </div> </body> </html> --_000_DB8P190MB0730A5E666636DC0871F162FF1AA0DB8P190MB0730EURP_--"Solved96KViews0likes6CommentsCopy contents of one mailbox to another
Good afternoon, I have a bit of an interesting issue. I have a department that has split into two departments. The "new" department, department1 is keeping the name of the old department, and therefore wants the shared mailbox associated with department1 (department1@domain.com) The new department, department2, has a new mailbox, department2@domain.com. Great. However, the new department wants all of the contents of the old mailbox, including all of the folders from department1@domain.com, copied/moved to the new mailbox, department2@domain.com, and department1@domain.com to essentailly start fresh and blank. I was thinking I could just rename department1@domain.com to department2@domain.com, and create a new mailbox called department1@domain.com - however that won't work because Exchange Online will keep the previous alias assigned to the original mailbox, and that isn't able to be deleted. So I thought I'd use Search-Mailbox to move all of the mail - Search-Mailbox -identity department1@domain.com -TargetMailbox department2@domain.com - however, this requires a TargetFolder to be specified. If I try to specify Inbox, it creates a subfolder under Inbox, with all of the folders/messages. If I specify / for root, the messages disappear, because the root isn't visible (they show up in a search). My question is, is there anyway to copy these messages, and folders, intact, from the one shared mailbox, over to the other shared mailbox so all of the folders etc. show up under root, and the messages that are in the inbox to into inbox, and sent items go into sent items, etc. Any ideas? I was hoping not to have to export to PST and import the PST. Thanks, Craig94KViews0likes6CommentsRebuild search index of a mailbox in Exchange Online
This was something new for me and couldn't find such a post here, so hereby I'm sharing the experience. One of our users showed me that there are some emails in her mailbox which can't be found by using search, nor in the Outlook 2013 rich client (in Online mode), neither in OWA. Tried to search for various texts and properties from those emails, but they was just 'invisible' for search. I've opened a case with the Office 365 support through the admin portal, and what they recommended was simply to run the following PS command: New-MoveRequest our_user@ourdomain.com It seems this, submitting a move request for that mailbox is the recommended way to force reindexing an ExO hosted mailbox. Once the move operation has completed (it takes a few hours depending on the mailbox size, progress can be checked with Get-MoveRequestStatistics) the mailbox got re-indexed, which fixed the search.93KViews8likes12Comments
Events
Recent Blogs
- We’re introducing new tenant-level outbound email limits (also known as the Tenant External Recipient Rate Limit or TERRL).Feb 24, 202552KViews4likes143Comments
- We are announcing a change in behavior of the EWSEnabled tenant-wide switch in Exchange Online.Feb 20, 202512KViews3likes17Comments