Need assistance: Unable to Remove GoDaddy as Partner/Reseller and Unfederate the Domain actus.law
I have been trying to resolve this issue for nearly four weeks, and been through many troubleshooting sessions and telephone calls with Microsoft Support, but this seems extremely complicated: The domain actus.law is owned by the Danish law firm Actus Law, and is registered with GoDaddy as the domain registrar. The Microsoft 365 tenant was originally created and federated by GoDaddy, who acted as the delegated administrator (via DAP/GDAP). On advice from a Microsoft Sales Advisor, Actus Law purchased a Microsoft 365 Business Standard license directly through Microsoft connected to the above tenant with the goal of managing the tenant independently through the Microsoft 365 Admin Center — without GoDaddy's involvement, beyond being the registrar. After the purchase it was impossible to manage users/licenses/domains in the Microsoft 365 Admin Center, as the domain is federated and therefore all requests always get redirected to GoDaddy. It was therefore not possible to verify the domain or create any users. I contacted Microsoft Support on 8 May, where I was told that the way forward was to delete current DNS records and remove GoDaddy's partnership privileges in the Microsoft 365 Admin Center. We therefore deleted all GoDaddy's delegated administrative privileges (GDAP/DAP) on 8 May 2025 and requested GoDaddy to end the reseller relationship. After this the support agent closed the ticket. This was handled through Support Ticket #2505081420003154. GoDaddy afterwards confirmed that they have removed all rights and that the domain is free to be unfederated. However, this did not solve the problem, since GoDaddy is still registered as partner and the domain is still federated. Therefore I am not allowed to make any changes and I always get redirected to GoDaddy when trying to manage anything in Microsoft 365 Admin Center. On 9 May I contacted Microsoft Support again and asked to disconnect the tenant from GoDaddy so I can manage everything in Microsoft 365 Support Center. This was under the Support Ticket #2505091420000046. The assigned agent tried during multiple weeks to troubleshoot and fix the problem with PowerShell commands using both MsolService and Microsoft.Graph, but always ended up getting access errors or insufficient privileges to perform the change in authorization from federated to managed. It has also not been possible to delete GoDaddy as partner. On 20 May I was asked to contact GoDaddy again to make sure that they had removed themselves as partner, and I got the following confirmation in writing from GoDaddy's Advanced Technical Support: "The Microsoft 365 organization for actus.law is no longer associated with GoDaddy. You can now reach out to Microsoft directly and receive support for a password reset for any admin user you need to access, or any other support issues. NOTE: If the domain is still set to use GoDaddy’s email login system you will need to ask Microsoft to “un-federate” the domain." On 21 May I explained GoDaddy's response in an email to the assigned agent, but now the agent simply stopped responding to my emails. I sent a reminder after 5 days, but did not get any response. On 28 May I called Microsoft Support and was assigned a new agent. That agent told me to contact GoDaddy, as it seems they still have visible GDAP, and only GoDaddy can remove that. Then the agent closed the ticket. I tried to contact GoDaddy afterwards, but they told me that the reseller relationship/GDAP was completely removed from GoDaddy's side on 8 May 2025 and all changes have propagated. However, since all GDAP/DAP had already been deleted at that point (which was done on 8 May, see above under number 4), GoDaddy could not remove it in Microsoft's systems according to the normal procedure so it is correctly reflected in the Microsoft 365 tenant. So they asked me to contact Microsoft Support again and explain the situation. WHAT I WANT TO ACHIEVE: I want GoDaddy completely removed as partner/administrator from my tenant and the domain actus.law to be "managed" and not "federated", so I can manage everything directly in the Microsoft 365 Admin Center and use my Microsoft 365 Business license. CURRENT STATUS: GoDaddy says everything has been removed on their end and that only Microsoft can now unfederate the domain. Microsoft Support says GoDaddy still needs to remove DAP/GDAP — but I cannot see their DAP/GDAPS anywhere in the Admin Center, and GoDaddy says they’ve already done it. Does anyone have an idea of what to do in this situation? I would appreciate any help, I feel completely stuck, and I am unable to set up any users or mails 😒
Microsoft 365 Apps Admin Center - Inventory Error
We're running into issues trying to access Inventory in the 365 Apps Admin Center (https://config.office.com/). When trying to swap a specific group of devices to a different update channel (Current to Monthly Enterprise), we go into the Apps Admin Center, select inventory and receive a generic error: There was a problem showing the security update status information. Please refresh the page or try again later. 00000000-0000-0000-0000-000000000000 This has been happening for 3 days now. Was working fine prior to that (and were able to flip a few devices earlier in the week). Anyone else experiencing the same/similar issues? Multiple 365 Admin's within our organization are getting the same error, so it's not isolated to 1 person/1 account.
Login problems, continuously getting the same message
Every time i login on an app i get the same message: "More information required" "Your organization needs more information to keep you account secure". Then i have the options to Use a different account or Learn more. I can just press Next and the message goes away. After that i get another message: "Keep your account secure" "Your organization requires you to set up the following methods of proving who you are." Below that, there is a message: "Success!" "Great job! You have successfully set up your security info. Choose "Done" to continu signing in". "Default sign-in method:" When i press done, the message goes away. But i keep getting the 2 messages every time i change an app or even a menu option. So to be clear, this happens every time i switch apps. I.e. from Exchange to Azure, to Outlook. When i press "Next" and "Done" i get access to the app. But this is really annoying. What am i doing wrong? I'm the admin of a small company, and i cannot figure out what setting i changed or need to change. The property "Enable Security Defaults" is already set to no.Creating an Office 365 User no longer lets you send email with password to User
Is this a new update? Before, on this page, when I wanted to create an Office365 User account, I had the option at the bottom where I could input an email so the User would receive the password for his first login, but the option no longer appears...
Any Work arounds for not being able to share mailboxes across Multi-Tenant Organizations?
Hi, Multi-Tenant Organizations make a lot of things fairly seamless, but you can't have a shared mailbox that is shared to users in two tenants within the organization. Which is a bit of a problem because I have a situation where that would be the ideal solution. So does anybody have suggestions for the next best thing?
Request to Reactivate Microsoft 365 E5 Developer Subscription (Subscription ID: sparkyy)
Dear Microsoft Support Team, My Microsoft 365 E5 Developer Subscription recently expired(2/22/2025 (UTC) due to an oversight during a busy work period. However, the subscription has been actively used for the following development activities: Microsoft Graph API Integration: Developed internal collaboration tools leveraging Microsoft Graph API . Critical Project Files: Stored core project documents, including key deliverables, in OneDrive/SharePoint. Automation Workflows: Utilized Power Automate for data synchronization tasks. I kindly request the reactivation of my subscription and commit to implementing automated renewal tools (e.g., GitHub Actions) to ensure compliance moving forward. I have use it over 4years that is very helpful for my work and Team, hope it 's able to back, I tried to send mail support@email address removed for privacy reasons, but didn't any message back.due to now already close 30days, I worry my project and files will be delete,Would you please help to me for the E5 account,Thanks for you all help. my admin account email address removed for privacy reasons my domain admin account email address removed for privacy reasons Subscription domain name: sparkyy Best Regards, Spark.YuanAdmin acces
As an organization we have an office 365 account, but we do not know who the admin/manager is. The suspicion is that it is someone who left the organization a while ago, which is why we do not have an active email address and/or password for those accounts. We cannot log in to the admin center because of this. Does anyone have a solution on how we can regain access to our office management? Telephone contact with MS has not helped so far because we do not know who the admin is and they keep asking for it or saying that we have to ask our admin.MTO and access to on premises file system
Let me preface this by saying I'm still fairly new to 365 Admin (it's been a steep learning curve) and haven't even got my feet wet with on premises stuff as yet. Also, I think some of the admin decisions made previously by others may have been based on just repeating what was found to work the first time rather than necessarily a deep understanding of the best solution. The situation when I arrived on the scene was this (actually it was a bit more complex and messy than this, but this simplified description covers the salient points at this stage) One tenant, with two domains, call them old-domain and new-domain. Two types of user, who I will refer to operations and corporate. An on premises Active Directory system running a file server. Well to be more precise on three premises with mirroring of data and a DFS, but from the user perspective when you're one of the office locations and connect to the network the same folders are available to you. Everyone was using Azure Joined Company Laptops to do this, so their laptop logins were also their network logins. Outside of the offices people connected to the DFS using a VPN (with three gateways in different countries). Operations Users had one account, @old-domain, this was licensed for 365 and had a mailbox associated with it. It was also synched to their on premises AD account Corporate Users had two accounts, one @old-domain with no license, synched to an on premises AD account. The second was new-domain with a 365 license and mailbox. If you're scratching your head wondering why two accounts rather than assigning the new-domain email address to the same account, I can't give you a definitive answer as I've never been given one, but for whatever reason when new domains were brought into play on corporate name changes the admins gave them new mailboxes rather than simply aliasing email addresses to the same mailbox (some people had three accounts as a result). What I did note was that when a new Corporate user was added the admins gave them both of the above accounts, I was told that the unlicensed old-domain one was required for the access to the DFS. Now for reasons not worth getting into here, a decision was made to move the Corporate users to a new tenant, along with new-domain and then to link the two tenants in a multi-tenant organization. It was also decided to leverage BYOD for Corporate users, so their devices will only be Azure registered. This has been done, there was some pain thanks to the reluctance of Microsoft applications to switch to the new account locations rather than redirecting back to the old tenant, but that's been sorted. So right now Corporate users still have two accounts, but on two tenants. On the Old Tenant they have their @old-domain account, no license, no mailbox, synched to the on premises AD (as before) On the New Tenant they have their new-domain account. This is where they actually do their work, and is the only account anyone should be communicating with internally or externally. Access to the DFS is being done using the VPN with the on premises credentials associated with the old-domain account. In terms of functionality, this works perfectly well, people across the two tenants appear in each other's address lists, they can chat and share information etc. Everybody also has access to the folders they should have access to on the DFS. However there are two issues. The first, and most detrimental in terms of just getting work done is that users in one of the overseas offices have found their access to the DFS has slowed considerably, despite being in physically the same location as the data. I believe the problem is that although the data is on-premises, the VPN gateway is not, therefore data does a round trip from the server, through that gateway IP address at the ISP and back to the user. Since they are in a remote location with poor internet this slows things considerably. So the first question is, how do we take that loop out of the equation so that when they are in the office they connect more directly to the servers on site? Ideally without having to revert to needing an Azure AD joined device. The second issue is that those remaining old-domain accounts (the ones for the Corporate users who are now working on the new tenant) on the old tenant are messy, in two ways 1) From an admin perspective, because every one of those corporate users still has two accounts, their local one that is synched to On Premises AD, and the the external account shared from the new tenant as part of the MTO 2) From a user's perspective. For reasons that I cannot fathom (but this is coming direct from Microsoft after many attempts on my part to find a way) it seems that while you can control which licensed accounts appear on Teams search by controlling whether they are in the GAL and setting the appropriate switch in Teams Admin, all the unlicensed users appear whether you like it or not. The net result is that when someone on the old tenant starts typing in a name of someone in Corporate, they get two suggestions coming up. So the second question is, are those accounts actually necessary?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?Where does Teams get its user list from? I can't make sense of which accounts I see vs which I can't
OK, so I have a currently rather unusual situation. I am looking at a 365 Tenant. A number of users have four accounts on the same tenant (let's not even get into why, cleaning things up is part of the reason I got called in). When you start typing their name into teams it comes up with three of them as a suggestion (I only want one) Account 1: has just been used for ActiveDirectory for permissions to the company's Distributed File System (stored in on on premises servers in various locations). This account has to the best of my knowledge never had a license or mailbox associated with it, and so has never been on the global address list, it's also never had the teams app enabled for it. I don't want this one to show, but it does Account 2: A now defunct account which used to have a Business Standard license assigned to it, but has now had the licensed removed. Before the license was removed this account was hidden from the GAL and its teams app disabled. I don't want this one to show, but it does Account 3: An now defunct account which still has a Business Standard license, but with Teams deselected in the Apps. I don't want this one to show... and it doesn't Account 4: An account shared via a multi tenant organization (the users in question have been migrated to a new tenant). So these are members (not guests) but external ones. I want this to show, and it does. Now, accounts 2 and 3 will be deleted soon, whether we can get rid of account 1 depends on whether the necessary access to the DFS can be done using account 4 (which I need to look into next). However for the time being they are all there so I was trying to hide accounts I don't want users trying to message on teams from teams, and I cannot make any sense of which I see which I don't. To sum up. Account that has never been on the Global Address List and never been activated for Teams - Shows Account that used to have a license and was on the GAL, and used in teams - Shows Account that still has a license, but has been removed from GAL and had teams app disabled - Doesn't show Account that has no license and is not on the GAL, but has teams on it's host tenant - Shows After a previous inquiry I set "Scope directory search using an Exchange address book policy" in the teams setup, but I have not set up any specific address book policy as yet. I have tried showing and hiding people from the global address list, and also the "ShowInAddressList" setting in Entra (which seems to only be available through graph?). Nothing seems to make a difference (it doesn't help that Teams takes forever to update its local cache for this stuff, so maybe a change DID make a difference at some point and I missed it). I cannot find any logic as to which of these accounts is showing in the auto suggests and which not, most notably that account 1 shows but account 3 doesn't. So, where is Teams getting its list of contacts from?
