Forum Widgets
Latest Discussions
Can't license 365 groups anymore
Ever since group based licensing was moved from Entra to 365 admin, it's no longer possible to apply licenses to to 365 groups. This is clearly broken and needs fixing. What's the process to raise this with Microsoft? I tried using Graph but that's also broken, even when following the MS doc. I raised a support case but they guy that called back was absolutely useless, didn't even know what I was talking about.
Mismatch between exchange recipients list and mailboxes set up in 365 Admin?
I'm a little new to 365 administration, so please excuse me if I am being a little thick here. I am looking at a 365 Tenant, there are around 100 licensed users (and therefore around 100 mailboxes allocated), but if I go to exchange admin and look at recipients, there are only 40, including shared mailboxes. My first thought was that perhaps only mailboxes that had actually been used were listed, but I checked one of the "missing" mailboxes in the 365 admin centre and apparently they have 8 Gigabytes of emails in that mailbox. Indeed the same user has three accounts, each with their own license and mailbox (don't ask why, I didn't set this up), I see two of them in the recipients list in Exchange admin. What am I missing?Can I hide user accounts from contact lists?
I'm dealing with a Tenant where for unknown historical reasons users have been given multiple accounts under the same name, but with different mailboxes and different email addresses (same name, different domain). I'm merging the mailboxes together, and aliasing the various email addresses onto the one account, so they only have to deal with one account going forwards. Until the users (and myself) are confident that everything that needs to be transferred from the now defunct mailboxes has been copied correctly I need to keep them there, but effectively inactive, so I gave them another email address which has never been publicised (actually using a spare domain already allocated to the tenant) thinking that it would be safe as noone would be sending emails to an address that never existed before. This all seemed to go swimmingly, until people said they had not received email and I saw they had been sent to the "secret" addresses. What I didn't count on was Microsoft 365 "helpfully" adding these addresses to people's contacts (I'm guessing through the global address book?), so when people (at least people within the tenant) send a new email and look up the details of that person they may get the entry which has the email address I don't want any new emails going to. I've set up forwarding to make sure people receive all their emails in their current mailbox, but I'd really rather they weren't ever sent to the "secret" mailbox in the first place. So is there a way to hide these defunct mailboxes? They are not supposed to be used to send or receive emails at this point, they're just being kept as a backup until we can verify the contents have been merged successfully into the current mailboxes.Exchange changes not propagating back to 365, but only for one account
So, I have a Tenant where, for reasons known only to previous admins, when company rebranding occurred, rather than setting up the new email addresses as aliases on the existing user mailboxes, a new mailbox for the new domain was created each time. As a number of people have multiple accounts with multiple mailboxes which I am currently merging together (using BitTitan MigrationWiz, which seems to be doing its part just fine). Now, for the purposes of this discussion there are three domains olddomain.com (the email domain before the rebranding, emails still get sent to that address daily) newdomain.com (the current preferred email domain) other.com (a domain they purchased and added to the Tenant but are not using, I am using it to park the older mailboxes after their contents have been merged into the current one). My procedure has been 1) set email address removed for privacy reasons as an alias on the olddomain.com account (for convenience in setting up migrationwiz) 2) Do a pre-stage merge of most of the olddomain.com mailbox into the newdomain.com mailbox 3) In 365 Admin, change the primary email of the olddomain.com account to be otherdomain.com 4) In Exchange, go to what is now the otherdomain.com mailbox and delete the olddomain.com alias from it 5) In 365 Admin, add olddomain.com as an alias to the newdomain.com 6) Finish the merge with MigrationWiz Now this worked apparently flawlessly for 7 people, then I encountered a problem with the 8th Everything went fine up until step 5, when I discovered that despite deleting the olddomain.com alias in Exchange, it still exists as an email alias in the email address removed for privacy reasons account (the one attached to the old maibox) in 365 Admin, so I cannot assign it as an alias to the email address removed for privacy reasons account Putting things back seems to work fine, changes I make in 365 admin seem to propagate pretty much instantaneously to Exchange, but the opposite is not the case. But so far only with this one account, not only have I executed the above procedure successfully with 7 previous users on this tenant, but I've done it with one more since this problem case popped up (and I've tried the problem case again since that successful operation, thinking it might just have been a glitch) but it still doesn't work. Does anybody have any ideas?
Force change password at next login on-premise and MS online
Hi Currently, I have a hybrid environment with AD on-premise, Azure AD sync (with password hash & SSPR), and Exchange Online. My goal is to force change the password at the next login from on-premise AD to MS online and vice versa. It's working. When I change the password on-premise AD, MS Online prompts me to change the password. It is not working when I set the account from the Admin center to force the password change at the next login; it does not sync to on-premise AD. The domain computer will not prompt to change password. Thanks in advance MS recommend to try this Install-Module -Name Microsoft.Graph Connect-MgGraph -Scopes "OnPremDirectorySynchronization.ReadWrite.All" Then run this command. $OnPremSync = Get-MgDirectoryOnPremiseSynchronization $OnPremSync.Features.UserForcePasswordChangeOnLogonEnabled = $true Update-MgDirectoryOnPremiseSynchronization -OnPremisesDirectorySynchronizationId $OnPremSync.Id -Features $OnPremSync.Features
User constantly prompted they need to request access to OneDrive shared item
Hello everyone! I have one specific user in my tenant who is unable to access files shared with them by their manager, (or anyone else for that matter.) They will continuously be prompted to request access to the item, which even granting direct access as opposed to sharing the link with them will loop them back to the same page. I took control of the manager's OneDrive directory and direct-shared the file myself to the user with no success and the same SharePoint access prompt. I additionally shared a file of my own for testing purposes, though this leads them back to the same page. All files within their own OneDrive on the app and on the web sync fine, they can also share files with other users---they just are unable to open anything shared with them. If this makes any sense? Has anyone encountered this and if so anyone have any suggestions for a solution? tldr; anyone who shares anything with one particular user they can't open it no matter what. Thanks. -TristanChange language of Notification Mails for User submitted E-Mails
Hello, I couldnt really find anything regarding this topic, but is there any way to change the language of the E-Mails regarding this topic: Admin review for user reported messages - Microsoft Defender for Office 365 | Microsoft Learn I know how to customize the E-Mails but the subject and general text are still in English and our customers are complaining about this.Integrated Apps & Central Deployment Fails
Issue with Integrated App and/or Central Deployment of add-ins ending with errors. After trying several different apps, for Excel or Word the process ends with a different error depending on which method is used. Integrated Apps, ends with a Failed Central Deployment, ends with “This operation was unsuccessful - reasons may include: Learn more about eligibility requirements.” We are trying to deploy the web version of the app All users have a Business Premium license all prerequisites appear to be fine tried 3-4 different apps using both methods, Integrated apps & Central Deployment (Add-in) using Global Admin account to deploy Tried setting everyone, dif individuals all fail We are trying to deploy an add-in for Excel web app, any assistance would be appreciated.Sender Rewrite
Hi, I'm looking at a scenario where a company has two Microsoft 365 tenants for different divisions in different countries. The issue is that they need to be able to have external email addresses with the same domain. Apparently this is a fairly common requirement when a corporate acquisition occurs (though most commonly for a short period until migrations can be done), so it seems it should be possible. There are various options for incoming email that seem to work such as email forwarding between tenants or an external forwarding service like improvMX (though it seems from what I'm reading there may be some DMARC issues associated with this approach?), the issue is giving outgoing email the correct "from" domain. Searching on the subject seems to touch on various possibilities, Exchange Edge Transport Server, SRS in Office 365, and even postfix, but it's all a bit unclear what is current, what is built into Microsoft 365 itself (obviously not postfix) or indeed what actually does what I'm looking for. So I'm hoping to avoid going down too many rabbit holes and dead ends by asking here.
Security Admin Center Tenant Allow/Block List Not Able to Block IPv4?
While using the Security Admin Center Tenant Allow/Block List we have been able to block specific email addresses and IPv6 IP addresses but are unable to block IPv4 IP addresses. We have tried both using the console and the CLI but have turned up unsuccessful both times when it comes to IPv4. A large majority of the phishing attempts that we encounter come from IPv4 addresses but we have been unable to block any of these. Will there ever be functionality for IPv4 within the Tenant Allow/Block list or is the only option to use conditional access policies? Also why is this enterprise tool only functional with IPv6 and without documentation stating that it does not work for IPv4?
