The regular members of the Team site should not be able to EDIT and/or DELETE pages, including but not limited to the homepage of the site. We have tried various tricks to achieve this via fiddling with SharePoint custom permissions, changing default permissions levels and reallocating permissions to the members group but they break connection to Teams in MS Teams and other office 365 shared services. We do not use SharePoint like Wiki where members should be allowed to add/edit pages, add/delete contents etc. This is a different use case and a major issue for organization, departments where someone goes in and deletes a major site page. We understand that you can manage permissions individually for each page but that is only a workaround not a viable solution for sites with lots of pages. With classic permission gone from modern Team site, there has be be a way to upgrade or downgrade what members can or cannot do on a site without compromising their office 365 shared service capabilities.

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.

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.

*English follows Japanese

■Title(件名)：
ProxyAddress を変更したい。
I want to change the ProxyAddress

■Description(内容):
Exchange Online の [連絡先] に外部ユーザーのメール アドレスが登録されている場合、"勤務先の電子メール アドレス" が空欄となり、SharePoint からの通知が届かなくなり、別途 "勤務先の電子メール アドレス" の登録が必要となる。
また、 連絡先に登録をする際に、重複のエラーとなる場合がある。
ゲストユーザーの ProxyAddress を変更する手段として、一度ゲストユーザーを削除して、ProxyAddress を重複しないように作成するコマンドを実行することで対応しているが、その場合は
ProxyAddress を登録することができれば SharePoint からの通知が届かなくなる。
ProxyAddress を変更することで問題は解消できると考えている。
ProxyAddress を変更する機能の実装を希望します。

In cases where the mail addresses of external users are registered in the “Contacts” on Exchange Online, “Work email address” becomes blank, notifications from SharePoint are not delivered, and one needs to register the “Work email address” item separately.
Also, when registering the contact details, there are cases where a number of overlapping errors occur.
In order to change the ProxyAddress of guest users, we are using commands to create ProxyAddresses that do not overlap, but then if a ProxyAddress can be registered, notifications from SharePoint stop being delivered.
We think the issue can be solved by changing the ProxyAddress.
Please add a way to change the ProxyAddress.

*English follows Japanese
■Title(件名)：
検疫されたファイルを、単独で選択した時に、[検疫から削除] ボタンが押せず削除ができないため、修正を希望します。
Quarantined files cannot be deleted without pressing the [Remove from quarantine] button if the files are selected individually, so please correct it

■Description(内容)：
現在、[Office 365 セキュリティ/コンプライアンス] - [脅威の管理] - [確認] - [検疫] 内の "ファイル" の検疫画面では、単独でファイルを選択した場合に、[検疫から削除] ボタンがグレイアウトして押せません。
しかし、複数ファイルを選択した場合は、[ファイルの削除] ボタンによる削除が可能です。
単独でファイルを削除できないのは、ユーザーにとって大きな問題です。
至急、修正されることを強く希望します。
Currently, on the "File" quarantine screen in [Office 365 Security / Compliance]-[Threat Management]-[Confirmation]-[Quarantine], the [Remove from Quarantine] button is grayed out when a file is selected individually and cannot be pressed.
However, if multiple files are selected, those files can be deleted by using the [Delete file] button.
Been unable to delete single files is a huge problem for users.
We strongly hope that this can be corrected urgently.

the option that I'm speaking about was avaialble before the office365 new view released and its a usefull link to us as we are controlling the sharing of OneDrive External sharing permission ,do the website updates and after the new view we did not find the option again !!
we open a support case to check the issue and they advised us to raise a UserVoice request to enable this option back .
your support is highly appreciated and have a great day .
my contact and details is available in my profile .
thanks and appreciated your prompt support .

*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.