Forum Widgets
Latest Discussions
Archiving Teams channels?
Hi, I found this from MS https://support.microsoft.com/de-de/office/archivieren-oder-wiederherstellen-eines-kanals-53c46491-a265-4391-a2a7-001c5026c9e5 But settings are not available as described in that article. Any ideas how I would be able to archive channels within MS Teams?SolvedheinzelrumpelJan 31, 2025Copper Contributor33Views0likes2CommentsO365 SSPR require users to register when signing in
Hi Everyone Can someone please shed some light on this. In Azure SSPR under password reset>registration> require users to register when signing in Yes or No. Below is MS website explanation. Does that mean if I set it to Yes, if users go to office.com they are prompted to register in SSPR? What are the down side of choosing no, You can enable the option to require a user to complete the SSPR registration if they use modern authentication or web browser to sign in to any applications using Microsoft Entra ID. This workflow includes the following applications: Microsoft 365 Microsoft Entra admin center Access Panel Federated applications Custom applications using Microsoft Entra ID When you don't require registration, users aren't prompted during sign-in, but they can manually registervirtual-techJan 30, 2025Brass Contributor33Views0likes4CommentsCan I remove/hide a user from Teams?
Is it possible to "disconnect" a user account (Business Standard license, so teams is included) from Teams, so it cannot send or receive chats, or join or be invited to teams? By way of explanation, I am dealing with a situation where a number of users had two accounts on the same tenant for "reasons" (happened before I got involved). I have merged (using BitTitan) the emails, contacts and calendars from the unwanted accounts into the users' primary accounts, but was intending to not delete the secondary accounts straight away for the sake of user confidence. So I changed the primary address of those accounts to a spare domain that was already set up in the tenant but they decided not to use (so the mailbox user(at)olddomain.com became user(at)sparedomain.com) and then aliased the user(at)olddomain.com email address to the primary account of user(at)newdomain.com My theory was that this would then mean that all emails would go to the primary account (since the spare domain has never been used in any communications before) but the users could still check their old mailboxes and calendars to reassure themselves they had everything before I removed the accounts completely. I didn't count on 365 "helping out" in the background. Where users were seeing "user(at)olddomain.com" in their Team app, they STILL see that, but confusingly behind the scenes, rather than those messages going to the same account an email sent there would, they go to the account that address was PREVIOUSLY allocated to, namely the user(at)sparedomain.com account which is supposed to be dormant. I can only assume that the routing has been automatically switched by 365 when I did the primary email juggling, but the client has not updated the display text. Anyway, I need to stop people from messaging those old accounts, but old habits die hard. I'd prefer to keep the accounts available (purely for viewing purposes) for a short while so users can reassure themselves (and me) that they have everything they need from them, hence the initial question.LeftyJan 29, 2025Copper Contributor31Views0likes1CommentExchange Online - Seeing all aliases of dist list
Hello all, We are preparing to sync our on prem AD distro groups and mail enabled security groups to O365, with a migration of email to EO to follow. (We already have user accounts synced via Azure AD Connect.) One gotcha, is that we have old email addresses (with unused domains) on these groups and I'm not sure if thats going to be a problem if I sync then before stripping those out. I was able to script removing those from the user accounts before we synced those, though doing it for the groups hasn't been successful so far. I went ahead and synced a couple of DG's to O365 just as a trial run, and when I view the groups in Exchange Admin Center / Groups/ Dist List, it shows the primary email email address and two of the alias addresses. Then it shows '+3 more'. I can't figure out how to view those '3 more' aliases. I'm wanting to see if those additional addresses are good addresses (with our domains that do exist in O365). If so, then I would seem that the sync leaves out the 'bad' addresses, if that makes sense. Thanks for any pointers!SolvedMauryJJan 27, 2025Copper Contributor29Views0likes2CommentsLost mfa global admin can not login, no break glass account
No partner or another global admin or break glass account. Yes I know thats a mistake but just need mfa reset for the global admin account. Hi. I have been calling ms support for multiple days, on hold for hours at a time. I know the story about getting hold of the data protection team and there hold times. I can't login to my tenant to open a case since I lost my mfa, changed phones and the restore is not working. Already tried sspr and thats not working either, my backup email is not getting the pin. Anyone as MS that can help open a case vs being on hold for days at a time. txs M35Views0likes1CommentEntra ID Allows People to Update their User Principal Names
Entra ID allows unprivileged users to update the user principal name for their accounts via the admin center or PowerShell. It seems silly because no justification for allowing people to update such a fundamental property is evident. Perhaps Microsoft has some excellent logic for allowing such updates to occur, but blocking access seems like the right thing to do. https://office365itpros.com/2025/01/24/update-user-principal-names/195Views2likes0CommentsCan 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.LeftyJan 20, 2025Copper Contributor55Views0likes1CommentExchange 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?LeftyJan 17, 2025Copper Contributor51Views0likes5CommentsMismatch 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?407Views0likes9Comments
Resources
Tags
- Microsoft 365 admin center660 Topics
- admin617 Topics
- office 365426 Topics
- Microsoft 365 Admin app87 Topics
- microsoft 36553 Topics
- exchange51 Topics
- Exchange admin center49 Topics
- Reports47 Topics
- security44 Topics
- azure active directory42 Topics