new mail-account automatically forwards external mails to internal address
Hi, last week I created a new mail-account to our outlook-users and added a mail-license. Only internal mails was received in the new inbox and after troubleshooting and using mail-trace I discovered that the mails was forwarded to another internal inbox. This is not something that is configured anywhere in the mentioned settings when trying to troubleshoot forwarding-issues. How do I turn this off, so that my new employee can receive external e-mails. We don't have any policies or rules set up, that should trigger this behavior. Regards Lars
I don't want 100 different SharePoint sites. How to create private teams w/o a new site?
Guys. WTF. I've inherited a problem where a company of 50 people has 100 sharepoint sites - because users created different Teams for different projects, and Microsoft makes it incredibly opaque what this actually means. Now we have 100 SharePoint sites, many of which are unused, but all of which appear in the list of sites in 365AC. The structure we WANT is 1 Sharepoint site for our 1 org, but multiple locations within that site, and multiple groups for multiple projects. I THOUGHT what could work was converting the excess Teams into Private Channels. But I have now learned that private channels ALSO create SharePoint sites, because _______. Most confusingly, all of these sharepoint 'sites' DO exist within our main SharePoint website - they're just pages (but not 'pages') pretending to be a fresh sharepoint website. This confuses the **** out of people, the way they've redefined what a 'site' is, what a 'team' is, etc. This is genuinely hot garbage, and it's suddenly clear to me why people always push back on using SharePoint over OneDrive. Recommendations for... not having this disaster? Making a structure that is intuitive and doesn't redefine what a site and page are, and allows you to have private locations for management or projects, but DOESN'T create a 'site' within the main 'site', with it's OWN 'documents', and it's own 'Notebook' (which isn't a document) and it's own 'Conversations' (which are NOT conversations), and it's own 'pages'? I don't work with dumb people - these are very technical people. But even our main SharePoint guy is mystified by these interactions. Does it make more sense in another language? If anyone at Microsoft is reading - the english term 'site', comes from the word 'website', which generally refers to a distinct web service with a distinct domain name. These contained different webPAGES.. When websites started existing off a shared domain name, like company1.sharepoint.com and company2.sharepoint.com - this confused people, but they put up with it, because it was relatively easy to explain the tech behind this - having websites under a single site, that wasn't too hard to understand. But what SharePoint seems to do, is extend this practice into absolute hysteria, where a particular webPAGE of a webSITE is ALSO a site, but also is a TEAM, or COULD be a CHANNEL. OR it could be a PAGE - WHO knows? If it's a TEAM, that TEAM could have CONVERSATIONS, which aren't actually Team Conversations - they're EMAILS. But this is fine, because all CONVERSATIONS of a TEAM done in TEAMS are actually stored as EMAILS so really those, CONVERSATIONS should be CONVERSATIONS... So why aren't these conversations in Teams between a Team that are stored as Emails not showing in the Conversations which show emails within that Team? aefggaddadsfasd
Stop Excel auto formating
How do I stop Excel from automatically formatting cells? I have three columns. The first column is formatted currency with fill. The second is text. The third is general. When tying a number in the general column Excel automatically formats the cell to currency with a fill matching the first column. How can I stop Excel from automatically changing the formatting of the cells in the third column?How to hide the Modify this view and Create View as per users available in groups
Hi All, I have classic view of SharePoint in list/libraries. I have group(for Managers). I just want want to show and hide the Create View/Modify View/Modify this view depends on users available in group. If user available in group(for Managers) then they can do anything like Create View/Modify View/Modify this view but if user is not a part of the group(for Managers) then they can not modify any Public views but the can create Personal view. Is there any way how I can achieve this functionality?
Inherited group-based license service plan checkboxes are now editable but fail on save
Hello, We are observing a possible UI regression in the Microsoft 365 admin center related to group-based licensing. Environment / scenario: - Microsoft 365 admin center - User-level “Licenses and apps” screen - The user receives the Microsoft 365 license through group-based licensing - The source group is a Microsoft Entra dynamic security group - The license and service plan settings are intended to be controlled at the group-based license assignment level We understand that when a license is inherited from a group-based license assignment, the apps/services for that inherited license should not normally be changed directly at the individual user level. The service plan configuration should be managed at the group/license assignment level. However, the current UI behaviour is confusing. Observed behaviour: 1. Open a user in the Microsoft 365 admin center. 2. Go to the user’s “Licenses and apps” screen. 3. The user has a Microsoft 365 license inherited from a group-based license assignment. 4. Some app/service checkboxes appear to be enabled and editable. 5. An administrator can actually clear/uncheck those checkboxes. 6. However, when clicking OK/Save, the operation fails with an error. In other words, the UI allows an administrator to make a change that cannot actually be committed. The reason this looks like a regression is that the previous UI behaviour was different. Previously, when a user’s Microsoft 365 license was inherited from a group-based license assignment, the relevant app/service checkboxes on the user-level “Licenses and apps” screen were greyed out or effectively read-only. Administrators could visually understand that those service plan settings could not be changed directly at the individual user level. Recently, those same checkboxes appear to be active and editable. The administrator can uncheck them, but the change fails only after clicking OK/Save. From an administrator UX perspective, this is confusing because the UI appears to allow an unsupported operation and only rejects it at save time. Expected behaviour: If service plan settings for an inherited group-based license cannot be changed at the individual user level, we would expect one of the following behaviours: - The checkboxes should remain disabled/read-only from the beginning. - The UI should clearly state that these apps/services are inherited from a group-based license assignment. - The Save/OK button should be disabled for changes that cannot be applied. - The UI should provide a link or guidance to manage the setting at the group-based license assignment level. Questions: 1. Has anyone else observed this recent change in behaviour? 2. Was this UI change intentional? 3. Is this a known issue or known UX regression in the Microsoft 365 admin center? 4. Is there any scenario where these checkboxes are intentionally editable for a user who receives the license only through group-based licensing? 5. Does this behaviour differ depending on whether the source group is an assigned security group or a dynamic security group? 6. Is there any recommended administrator workflow when troubleshooting service plan settings for a user whose license is inherited from a group-based license assignment? To clarify, this is not a question about how group-based licensing works. The concern is specifically about the UI behaviour where inherited license service plan checkboxes were previously greyed out, but now appear editable even though the change fails on save. If this is not intentional, it would be helpful if the Microsoft 365 admin center could restore the previous read-only/greyed-out behaviour, or clearly explain in the UI why the change cannot be saved. Thank you.
Circular Reference Issues - A desperate woman needs help ASAP =(
I have an incredibly in-depth spreadsheet, with about 15 pages, and in-depth tables and calculations on most of those pages. Point being, I have a HUGE freaking file with tons of data collected over the years. Now, all of a sudden, I cannot input anything without the Microsoft Excel Warning popping up, stating: "There are one or more circular references where a formula refers to its own cell either directly or indirectly. This might cause them to calculate incorrectly. Try removing or changing these references, or moving the formulas to different cells." I understand what this pop up is saying, but my file is so huge, and there is so much information, I cannot find the error anywhere!!!!! And I don't have the option to search for it. So I cannot correct this error on my own, and I cannot input anything into the spreadsheet without having to exit out of that **bleep** pop up!!! I am defeated, INCREDIBLY FRUSTRATED, and I cannot see a clear path to recovery. I have been working on this document for years now, and I cannot start fresh. HELP, HELP, HELP!!!!!!!!!!!!! SOS!! Anyone! I am desperate and beyond frustrated =(
Accessing External Sharepoint Site
I am able to access internal Sharepoints within my company and have up until now been able to access Sharepoints outside the company. When I now try to access an external Sharepoint, I get the following message on the external company's landing page. "Your account has been locked. Contact your support person to unlock it, then try again...." The external company states they have not made changes any access protocols. Likewise, my company says nothing has changed with respect to the rules/ability to access external Sharepoints. Someone indicated that the Microsoft “federation” settings/setup of the two companies may (now) be incompatible. Has anyone encountered this issue?
Why is Microsoft 365 setup (Groups + SharePoint + Domains) still so complex?
Microsoft 365 Setup Feedback Summary Summary of Experience: Setting up two small business workspaces (Cork & Clarity and Stone Clarity Consulting) in Microsoft 365 required navigating multiple disconnected systems including the Admin Center, Outlook, SharePoint, and an external DNS provider. The process was significantly more complex than expected and not intuitive for a non-technical user. Key Issues Encountered: 1. Identity and Account Confusion - Unclear whether to create separate users or use one account with aliases - Creating multiple users caused login confusion, broken permissions, and access issues 2. Domain and DNS Setup Complexity - Required switching between Microsoft and external DNS (Looka) - Instructions were unclear and required manual troubleshooting - No clear distinction between required and optional DNS records 3. Default Domain Confusion - New groups defaulted to the wrong domain - No visible option to change domain during group creation - Required changing global default domain (non-intuitive) 4. Inconsistent Group Behavior - Outlook groups and Teams-backed groups behave differently - No indication of differences or consequences - Groups appeared in some places but not others 5. Membership and Ownership Issues - Group creator was not consistently added as member - Ownership did not always persist after changes - Groups existed but were inaccessible or invisible 6. Outlook UI Limitations - Groups not visible despite existing and being correctly configured - No clear instructions on how to 'activate' or 'follow' groups 7. SharePoint Site Not Created Automatically - SharePoint sites were not created when groups were created - Required hidden steps: Outlook → Files → Open in SharePoint - No indication that the site did not exist yet 8. SharePoint Discovery Issues - Sites do not appear until manually accessed or followed - No onboarding or guidance for discovering sites 9. Ghost/Deleted Items Still Visible - Deleted group (Cork & Clarity Hub) remained visible - No clear distinction between deleted vs followed sites 10. Fragmented User Experience - Required switching between multiple platforms - No single place to manage or understand setup status - High cognitive load for basic configuration Conclusion: While Microsoft 365 is a powerful platform, the initial setup experience is overly complex and fragmented, especially for small businesses. Simplifying group creation, making SharePoint provisioning automatic and visible, and improving UI consistency across apps would significantly improve usability and adoption.
