microsoft 365 admin center
680 TopicsAgent in SharePoint option is not visible in the M365 admin center
Agent in SharePoint option is not visible in my M365 admin center under pay as you go service and it's only show Syntex services option not the Agent in SharePoint. As before we were able to see both options like Agent in SharePoint and Syntex services but now Agent in SharePoint is not visible. I have also attached the screenshot where both of the options were visible but now the Agents in SharePoint option is not visible, so is there new update in admin portal or is this is some kind of issue?Solved81Views0likes3CommentsBooking not available for everyone
Dear Community, We are currently experiencing an issue within our tenant related to the Microsoft Bookings App. While the app is enabled and accessible via browser for users in a specific group, some users are unable to add the app directly to their Teams interface without submitting a request. At this point, we have not been able to identify the root cause of the issue. I might be a policy issues that only we can solve. Has anyone encountered a similar problem or could suggest possible solution? Thank you :)48Views0likes2CommentsNot able to logon office 365 account or change it
If I want to logon to my Office 365 account I have to enter my emailaddress. Its is an @.onmicrosoft.com account. Entering password is ok, but then I am have to verify my phone number. The last two digits are shown, but clicking on this phone number I am getting an error like: 399287. There is no way of resetting this. I already contacted helpdesk but they cannot solve this problem. I have a bussniess account and I need some help about this. Every time I want to reset or want to make a change the account I am stuck in this error screen (endless loop). Please help me.216Views0likes4CommentsEmails from our custom domain ends up in quarantine
Hello, I have an issue with emails coming from one of our custom domains being detected as phishing for identity theft reason. We've got the main domain on Microsoft 365, let's call it: "domain-example.com" and the second domain on IONOS : "domainexample.com" When we receive emails from this second domain it is detected as phishing since it is a domain name very close to our main domain, therefore those emails are placed into quarantine. How do I resolve this issue? Can I indicate Microsoft 365 that this second domain is owned by our company, therefore the emails coming from this domain aren't identity theft attempts? I found how to add a domain on Microsoft 365 Admin Center but I don't know what are the consequences of this action, I want to keep my domain on IONOS and send emails from their web server. All I want is to stop emails from our company to end up into quarantine or spam folder. Thank you.Solved152Views1like4CommentsPeople Settings Appear in the Microsoft 365 Admin Center
The Org Settings section of the Microsoft 365 admin center has a new People Settings section where you can choose properties for the Microsoft 365 profile card instead of using PowerShell. The kicker is that the old method of using Exchange custom properties to customize what appears on the profile card is being replaced with standard Entra ID properties. A migration is needed, and it’s easily done with PowerShell. https://office365itpros.com/2025/09/04/microsoft-365-profile-card-2/113Views0likes1CommentNeed 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 😒205Views0likes2CommentsUnable to whitelist quarantined emails
We have an email that is being constantly quarantined from a webform. The email comes from the email of the web form server, but is spoofing an internal address in our tenant by design. The email keeps getting blocked, and nothing we've tried as far as transport rules, whitelist additions, etc has been able to discernably affect this. There is a option to create a tenant allow list entry but the maximum duration is 45 days. We need a way to reliably whitelist an email indefinitely.97Views0likes1CommentError importing Project Accelerator for Project on the web in power apps
I want to import the Project Accelerator solution for Project for the web (Project Plan 3). The solution can be downloaded form github https://github.com/OfficeDev/Project-Accelerator I am using a 30 day free trial version of M365 Business premium and Project planner premium with Project Plan 3. The suggested method to install the solution (as per above github repo Maintained by microsoft) is using http://powerapps.com > solutions > import solution upload the zip file download from the github page. I have global admin rights and using the default environment, and Rights to create Power Automate flows using the Common Data Service connector. However, when I get the following error message Solution "Project for the web Accelerator" failed to import: OptionSets import: FAILURE: SecLib::CheckPrivilege failed. User: XXXXXXXXX-XXXXX-XXXXXX, PrivilegeName: prvCreateOptionSet, PrivilegeId: XXXX-XXXX-XXXXX Required Depth: Basic, BusinessUnitId: XXXXX-XXXXXX--XXXXXX, MetadataCache Privileges Count: 5443, User Privileges Count: 1632 I am login in as the global administrator so all permissions must be already in place. In the Power Platform Admin Center, Environments > Settings > Users + Permissions > Security Roles and checked the user's assigned roles. All seems ok. Any help will be most useful.75Views0likes1CommentAny 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?848Views0likes5CommentsExtend M365 Archive Quota capacity
In my organization, we are currently on the O365 E5 License with default 100GB mailbox size per user and 1.5TB archive quota. However, due to organizational policy and regulatory requirements, we are expected to keep all the data from inception. Hence, the requirement for a solution to extend our archive size from 1.5TB. From the official Microsoft documentation, https://learn.microsoft.com/en-us/office365/servicedescriptions/exchange-online-archiving-service-description/exchange-online-archiving-service-description#archive-storage-quota the maximum expansion of the archive mailbox is 1.5TB. Is it possible to extend the archive storage to an Azure blob? Like an automated script that moves the data from the Archive mailbox for each user to the Azure blob or any other storage service that does not have storage size limitation. I am open to suggestions. Thanks234Views1like2Comments