Forum Widgets
Latest Discussions
How do you make a Shared Mailbox the default Send From account? (New Outlook)
I'm using Outlook for Windows version 1.2025.109.100 (on behalf of another user). I'm reading some suggestions online that say you need to add the account to Outlook first before making it the default Send From. I'm also looking at the Help section in Outlook that directs you to change this in the Compose and Reply settings. However, it's not possible to sign into a mailbox that isn't a user. I thought you used to be able to 'sign into' a shared mailbox using your own account but that is not the case now (perhaps it never was?). What it seems like is that we instead need to convert "Accounting" to a User account, give it a license, then sign into it in Outlook. That's not a Shared Mailbox - that's a user mailbox. I don't want to create a point of weakness for a potential cyber-attack (which we've had several). I can't really set up MFA for this account that no one can maintain. And I really don't want to have to spend money on a license to do something just because one piece of software is incompatible. Having to repeatedly instruct people and then repeatedly remind them to change their FROM account is just bonkers. On Outlook for Mac, as long as you're in the Shared Mailbox, the default FROM is that mailbox. (but, don't get me started on how much better the Mac version of Outlook is than the Windows version - see: All Accounts)Anthony-123Jan 15, 2025Iron Contributor55Views0likes1CommentExchange Online Powershell not connecting in scheduled Task script
Hello everyone, I am having this issue where I can't find any useful answer. We are connecting to Exchange Online with certificate based authentication and it works fine when we run the script manually. Running the script via scheduled task with the same user, we always receive the following error messages. PS>TerminatingError(Get-ConnectionContext): "One or more errors occurred." PS>TerminatingError(): "An error occurred while sending the request." An error occurred while sending the request. At C:\Program Files\WindowsPowerShell\Modules\ExchangeOnlineManagement\3.5.0\netFramework\Exchange OnlineManagement.psm1:762 char:21 + throw $_.Exception.InnerException; + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (:) [], HttpRequestException + FullyQualifiedErrorId : An error occurred while sending the request. This is the command we use to connect: Connect-ExchangeOnline -AppId $AppId -CertificateThumbprint $CertificateThumbprint -Organization $Organization -ShowBanner:$false -loglevel all Has anyone experienced this before? ExchangeOnlineManagement Module is Version 3.5.0 Powershell Version is5.1.14393.7155SolvedPatrick0411Jan 13, 2025Copper Contributor707Views1like8CommentsExchange SMTP Auth Fails with: 451 4.7.0 Temporary server error. Please try again later. PRX5
Office 365 refuses SMTP authentication with error: 451 4.7.0 Temporary server error. Please try again later. PRX5 This is when accessing External Send SMTP AUTH through OAUTH2 authentication. Initial authentication is successful (and is logged as so in Entra ID) but when trying to send send messages through authenticated SMTP, you get the above error. Working with multiple support reps, we looked through login logs and could not find any trace of the error in Entra ID. Support reps all blame the third party application. The issue is connected to a special use case, where a user has both the GLOBAL ADMIN role, as well as certain other admin roles. When you have a certain combination of those roles, for a selected user, OAUTH2 will fail, even though OAUTH2 for (apparently) ALL OTHER SERVICES - work without error! - ONLY SMTP Auth is affected. RESOLUTION: Keeping Global Admin while simply removing excess roles will almost immediately resolve the issue. This bug has been publicly noted as far back as August 2022, perhaps earlier. This needs to be fixed.GraphBuilderJan 13, 2025Copper Contributor855Views2likes10CommentsOOF to personal emails dropped at EOP relay
Issue: When an OutOfOffice recipient is gmail.com, outlook.com, msn.com ,etc, relay is dropped by EOP. Oof is delivered when recipient is an M365 tenant. Any other mail flows no issues to gmail and other personal addresses as well. It's only OOF to personal addresses. Env: Exch 2016 with EOP send/receive (hybrid manually, not hcw) We found 2 blog posts might be relevant, but these instructions did not resolve: https://techcommunity.microsoft.com/blog/Exchange/updated-requirements-for-smtp-relay-through-exchange-online/3851357 https://techcommunity.microsoft.com/blog/exchange/enhanced-filtering-for-connectors---improving-deliverability-and-minimizing-fals/4160483 This is what we see on the smtp protocol log: >,MAIL FROM:<> SIZE=7072, >,RCPT TO:<****@gmail.com> NOTIFY=NEVER, <,250 2.1.0 Sender OK, <,550 5.7.64 TenantAttribution; Relay Access Denied [*****.eurprd03.prod.outlook.com 2025-01-04T14:03:21.934Z *****], >,QUIT, ### We also looked into dkim, but finally found this line: By design, Exchange Online Protection uses the high risk delivery pool (HRDP) to send OOF replies, because OOF replies are lower-priority messages. https://learn.microsoft.com/en-us/exchange/troubleshoot/email-delivery/understand-troubleshoot-oof-replies#what-are-out-of-office-replies We feel this is not likely a connector or ceritifcate or onprem issue, rather something with HRDP and OOF in EOP. Could you confirm we are on the right track now? If not the Exchange Team can help please let me know who. ThanksJNLVKJan 13, 2025Copper Contributor47Views0likes3CommentsMove request falsely stuck
We are migrating mailboxes cross forest between two Exchange organizations and are having an issue with 3 of them. We were migrating these 3 mailboxes when the target Exchange server had the log disk filling-up, and move request seemed to be stuck. We extended the disk and the move actually completed, we check the get-moverequest for "non completed" and none was reported. We move the mailbox database, on the target DAG, between the two hosts and then, not sure if it's related, the get-moverequest reported three entries in "waitingforjobpickup" even if the migrationa has successfully completed, the mailbox is active on the destination and users are connecting without issue. How can we clear the status correctly or we just can delete the move request ? thanks SCStefanoC66Jan 13, 2025Iron Contributor26Views0likes1CommentAccess to Exchange Admin Centre blocked using most (but not all) URL links
Suddenly, when I try to use most of the published links to the Exchange Admin Centre, including the links on the Microsoft 365 Admin Centre, my access to the Admin Centre for Exchange is blocked. The messages vary but the most common one is "admin.exchange.microsoft.com closed the connection". All of the links for the other admin centres work just fine for me (Teams, InTune, SharePoint etc.) - it's just the Exchange Admin Centre link that are mostly problematic. Two examples of links that don't work for me: https://admin.exchange.microsoft.com/?landingpage=homepage&form=mac_sidebar https://admin.exchange.microsoft.com/#/homepage The only link I can find that still does work for me: https://admin.cloud.microsoft/exchange#/SolvedInaurukunJan 12, 2025Brass Contributor112Views0likes2CommentsExchange Online courses
Hello all, Since Microsoft ended the MS-203 certification and courses, there is no training available anymore. On the Micorosft Learn website there aren't courses about Exchange 365; only the 'manage complaince in Exchange 365'. Does any of you know if there will be a new training for Exchange 365 soon? Where do you find courses for Exchange 365 (and Defender for Office/Exchange). Kind regards, ArjanArjanBroekhuizenJan 10, 2025Brass Contributor79Views0likes2CommentsUnable to change mailbox permissions
Hi, We have inherited a Hybrid Exchange environment. It consists of 1 on-prem Exchange Server (Version 15.0 (Build 1473.3)) and M365. All the mailboxes have been migrated to M365 and ADSync is present to replicate to M365. The issue we have is that even as a Global and Exchange admin in M365, we are unable to edit the permissions of any users mailbox. Doing this via the M365 admin centre just returns a message saying "Something Went Wrong." If we try it in Powershell we get a "User is not allowed to call" message. We are trying to understand if this is an issue with M365 or we are trying to make the permission change from the wrong location? In a hybrid environment where all mailboxes have been migrated, from where you should you make permission changes to a mailbox? Is there something else we are doing wrong here? Thanks DBdbrenserv2024Jan 08, 2025Copper Contributor113Views0likes4CommentsMS Exchange SE 2025
Recently, I came to know that MS will next Exchange in Subscription Edition (https://techcommunity.microsoft.com/discussions/exchange_general/exchange-server-subscription-edition-arrives-in-summer-2025/4133577). The MS exchange 2025 will be the update of 2016 and 2019 version and 2016 and 2019 support will be the end of 2025. My query is new MS Exchange 2025 SE will be on-prem or cloud-based. If it is cloud-based, then the Active Director will be cloud-based, too. Can anyone clarify me those things.rockbdJan 07, 2025Copper Contributor269Views0likes4Comments
Resources
Tags
- exchange online2,420 Topics
- Exchange Server2,209 Topics
- office 3651,192 Topics
- hybrid825 Topics
- 2016724 Topics
- outlook717 Topics
- admin646 Topics
- 2013275 Topics
- 2010159 Topics
- 201969 Topics