The issue occurs when multiple users are collaborating on a file and one (or more) user is disconnected from the internet. Once the user is reconnected, the user either saves an updated version (i.e., updates to the previously opened version) or saves (or auto-saves) the previous version. This will overwrite any updates made by other user(s) while the user was disconnected.

Here’s an example that outlines the scenario:

1. User 1 opens the file and views current version A.




2. User 2 opens the same file and views current version A.




3. User 2’s internet is disconnected while viewing version A (e.g., due to spotty connection or the user closes the laptop). If the user updates the file while the internet is disconnect, the system shows that the upload is pending.




4. User 1 updates version A and saves it as version B.
   User 2 does not see version B since his internet is disconnected.




5. User 2’s internet is reconnected and his version is saved as version C. This overwrites User 1’s updates made in version B.

Unfortunately in this scenario, User 2 does not receive an error so the user isn’t aware that the versions are out-of-sync when he saves the file or the system automatically saves the file (if auto-save is enabled).

The system should at a minimum alert the user that his version is out of sync with the version in SharePoint and not allow the user to overwrite the current version.

If an Organization (Customer) has more Companies placed around the world they may have work processes and requirements separately for each. Therefore they may require to use Sharepoint for each Company separately with own URL/domain. It has simple solution to create new tenant. But if they are using and have active licenses of Academic or Non-profit type it may causes problems to build new tenant. Also there may be another requirements to share Calendars of users between more Companies stored in current tenant. In the past there can be used Public Website with Subsite (with canceled inheriting permissions) for it. If Public Websites are not allowed anymore there is no option how to achieve it. Thank you. Alexander

Currently in the Unmanaged devices setting in the SharePoint Admin portal you can allow full access, limited access or no access to all sites from unmanaged devices.

If you wish to give full access to just a few of your site collections and restrict access on all the rest you need to allow full access, then use PowerShell to restrict access on all sites and use PowerShell again to allow full access to a particular site collection.

The problem is everytime a new site collection is created you need to run PowerShell again on each new site to restrict it. When site collections are created regularly in your organisation this is not manageable. It would be ideal to have the ability to automatically restrict all newly created sites so that only the ones specified to have full access have this setting applied.

Please Make it possible to magage Admin permissions or Access to Tools based on azure ad Groups instead of individual users. This is important to create a proper user lifecycle and increase our security level.

If permissions are granted based on individual users instead of Groups, there is a danger that permissions are not being deprovisioned when a user changes his Team, especially when permissions are being managed at so many places as it is at the Moment (O365 Admin Center, Yammer, Security & Compliance Center, Compliance Manager...)

If permissions are granted for a Group, you just have to remove/add the user from that Group, so he loses/gains all the permissions connected to that Group. That would be a huge win for establishing compliance on our System.

*English follows Japanese
■Title(件名)：
ワークフローのエラーを検知、確認する機能
Features to detect and check workflow errors

■Description(内容):
ワークフローで予期せぬエラーが発生した際、実行結果からエラーを確認することになります。
実行毎に当該ワークフローからエラーを確認するのでなく、ワークフローのエラーを検知および確認ができる機能の拡充を希望します。
ワークフローで事象が発生した際、事象の改善確認を行う場合などにおいて当該ワークフローの再実行が必要となり、本番環境に影響が及ぶため、ワークフローを実行せずともエラーを検知するような機能が実装されると利便性の向上が期待できます。
When unexpected errors occur in workflow, users need to find the execution results to check for errors.
We hope that features to detect and check workflow errors can be implemented instead of having to check the errors from the relevant workflow on every execution.
When something happens in workflow, the relevant workflow needs to be executed again when confirming that the situation has improved etc, which affects the production environment. Therefore if a feature that can detect errors without executing the workflow is implemented, we can expect the whole process to become more user friendly.

This service really needs to come back the environment. I opened a ticket because I was receiving messages that this was broken - not knowing that it was not in service. Someone else in my environment was able to pull the same report with any problems. (Not sure what is going on there)
This feature gives us an and ideal report of content usage and view events for that is consider very important to where an end user is viewing content on our sites.

I am using a combination of reports- when I should or could just pull one report to view all that I need. This is too much for me whereas - to going thru several areas to pull some content modifications information - instead of just clicking once and wait for the entire result at once.

I also would like to see the return of this feature.