Setting up mail forwarding of an account with no Outlook license
Hi, Currently we have an account that can be used to log into office.com. There's no Outlook license applied to the account. As a result, if someone sends an email to it, it will be sent back because it's not a valid email address. (e.g. due to not having a license, there's no mailbox). I was wondering if it's possible to setup mail forwarding on this account? Or would it require an Outlook license? Sincerely, Jason
Moving Exchange Account Source Account
I have a very complex environment I'm hoping someone might jump start my search. We have two domains syncing to Entra ID. One domain is a resource forest where our Exchange environment sits. That domain contains disabled stub accounts synced to our primary domain where the actual user accounts sit. The source for all EXO mailboxes are the stubs in the resource forest. Those accounts are kept in sync using FIM 2008. We're wanting to decom that entire resource environment and move all of the attributes to the primary domain. The resource domain schema is the last version of Ex 2016. The primary domain schema is Ex 2010 SP1. I know my first step is to update the primary schema, however, has anyone encountered a situation like this? Any help would be greatly appreciated.
Graph http 449 throttled
We are experiencing a lot of Microsoft Graph trolling errors from some of our applications that are hosted in Azure Web App Services and other third party such as Front App to name one. I am trying to find an approach or strategy to figure out and narrow down what may be causing so many of these events. Whether I can narrow down by application or process, I am not sure yet. We enforce MFA on all our users, but of course, on Azure Enterprise Applications, we don't, which are used extensively in our ecosystem of apps. Any help is much appreciated here.
Email sent from Shared Mailbox gets stuck in Outbox
Hello, I am working with a client who has a primary and shared mailbox in Outlook. They are using the newest version of classic Outlook desktop app and they have full permissions to the shared mailbox, including "send as" permissions. They can send email from their primary mailbox without issue. However, when they send email as the shared mailbox, it gets stuck in the Outbox and never sends. I have tried the following: 1. Removing the profiles re-adding 2. Deleting the Outlook data files 3. Reducing cache to as low as 3 months 4. Turning off cache but when I do the shared mailbox gets an error that it cannot connect to the Exchange server 5. Turning on auto-archive to shrink the data files 6. Switching to "New Outlook". This does seem to work but the company uses a plug-in for a program called "Mail Manager" and they don't fully support New Outlook yet Sometimes these solutions will fix the issue for a few days to a week but then it begins happening again. This issue does not happen when they are using the mobile or web clients. To me this sounds like a corrupted data file but I can't pinpoint what exactly is causing the corruption. Any suggestions? Thanks, MikeSynchronization issue in New Outlook for Mac – ״Failed to refresh subscriptions.״
Hello, I am using Microsoft 365 (Exchange Online) on Mac, running macOS 26.1 (Tahoe). My Outlook client is: Outlook for Mac Version 16.103.3 (25113013), with a Microsoft 365 Subscription license. Since yesterday morning, in the New Outlook interface, my inbox has suddenly appeared empty, and I constantly receive the following error message: “Failed to refresh subscriptions.” It’s important to note: In Legacy Outlook, everything works perfectly. The web version and the Outlook app on my mobile phone also work well. The issue persists regardless of the network I am on (home, office, cellular, etc.). Troubleshooting steps I already tried: • Updating Outlook to the latest version • Removing and re‑adding the account • Clearing cache and preferences • Formatting my Mac and reinstalling everything from scratch Unfortunately, none of these steps has resolved the issue. Is this a known bug, and is there a recommended workaround or an upcoming fix? Appreciate assistance on that issue.
