■Title(件名)：
[サイト所有者] の画面表記が不正
[Site owner] screen display is incorrect

■Description(内容):
[サイト所有者] が本来は [Company Administrator] と表示されるべき以下の画面で 16 進数の ID の様なものが表示されている。

<従来の SharePoint 管理センター>
[サイト コレクション] - ルート サイト コレクションの [URL] をクリックした [サイト コレクションのプロパティ] 画面の [プライマリ管理者] 項目

<新しい SharePoint 管理センター>
[サイト] - [アクティブなサイト] でルート サイト コレクションを選択し、画面右上の [!] アイコンをクリックした [ポリシーの管理者] 項目

<その他情報>
・ ルート サイト コレクション以外のサイトコレクションでは事象は発生しない
・ ルートサイトを選択し、[所有者の管理] Company Administrator と表示される

<要望>
本来表示されるべき [Company Administrator] が表示されるよう改修を要望します。

The following screen where [Site Owner] should originally be displayed as [Company Administrator] shows something like a hexadecimal ID.

<Classic SharePoint admin center>
Site Collection-The Primary Admin item on the Site Collection Properties screen when you click the URL of the root site collection

<New SharePoint admin center>
Site-Active Sites, select the root site collection and click the "!"

<Other information>
・ No events occur in site collections other than the root site collection
-Select the root site and [Manage Owner] is displayed as Company Administrator

<Request>
We request that the [Company Administrator], which should be displayed, be displayed.

*English follows Japanese
■Title(件名)：
社外にサイトを共有する際に、組織ドメイン部分を公開しない設定を要望します
Request for a setting to not disclose the organization domain when sharing a site outside the company

■Description(内容):
社外にサイトを共有する際に、組織ドメイン部分を公開しない設定を要望します。
独自ドメインをテナント内に設定している環境で SharePoint サイトを作成した際に、URL 部分に組織ドメイン ("https://.sharepoint.com/&quot; の "" 部分) を表示しない設定を要望します。
この項目を設定等で独自ドメインと既定のドメインの切り替えなどができるようになると設定も容易にでき管理がしやすくなります。​
We will like to request for a setting to not disclose the organization domain when sharing a site outside the company.
We hope for a setting that will not display the organization domain part (the DOMAIN part in https://DOMAIN.sharepoint.com/) when creating a SharePoint site using a tenant enviroment that has set own domains.
If this setting can be used to switch between own domain and default domain, both settings and managing becomes easier.

Update get-credential to support Multifactor authentication.

I have 500 SharePoint Online CSOM scripts, and they authenticate with

$SPOcredentials = Get-Credential #-username $username -Message "Please enter the password for $Username to use SPO Cmdlets"
$CSOMCredentials = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($SPOcredentials.Username, $SPOcredentials.Password)
$Ctx = New-Object Microsoft.SharePoint.Client.ClientContext($WebURL)
$Ctx.Credentials = $CSOMCredentials

However, this is not supported when the account requires MFA.

There is a way to establish a context with the PnP AuthenticationManager;

Connect-PnPOnline -returnconnection -useweblogin -url $weburl
$authManager = new-object OfficeDevPnP.Core.AuthenticationManager
$WebCtx = $authManager.GetWebLoginClientContext($WebURL)

but it results in a Ctx with no Credentials parameter, and this causes most of the interesting parts of my scripts to break including all load-csomproperties calls (which you can get around by loading each property tediously one at a time, but crucially kills any CAML queries. Without this I can't load all items in a list, which is vital.

$camlQuery = New-Object Microsoft.SharePoint.Client.CamlQuery

            $camlQuery.ListItemCollectionPosition = $position

            $camlQuery.ViewXml = $CAMLXML

        # Executing the query

            $currentCollection = $List.GetItems($camlQuery)

            $WebCTX.Load($currentCollection)

            Execute-QueryRespectfully -Ctx $WebCtx -retryAttempts 5

After the SPOSiteSwap document links don't work anymore. The link has been updated but it is not correct so you get a 404 error.

We want to archive the actual root site of our SharePoint. But the site contains a lot of linked documents. After the SPOSiteSwap the links won't work anymore and the SharePoint site is not usable anymore.

Here is an example of the problem:
We have a link stored in a SharePoint List.
Before the SWAP the url is something like: https://tenant.sharepoint.com/:x:g/subsite/...
After the SWAP the url is modified like:
https://tenant.sharepoint.com/sites/archive/:x:g/subsite/...

But this link does not work. It should have been modified to https://tenant.sharepoint.com/:x:g/sites/archive/subsite/...

The part "/:x:g" must be at the right place so the link could still work.

Being able to set the Everyone except external built in role with read only permissions on a site collection from within SPO Admin portal would be useful.
We can already set admins but the next most useful manual permissions task is the read only role for a global user context.

We will utilise PowerShell and Site Designs to properly manage this but being able to set this from the Admin portal would be useful. Particularly when building new intranets and demo sites for dev/sales purposes. I'd use this feature on a daily basis. Much easier than having to go into the old Visitor group permissions page to set read only access to share new intranet designs with clients/users that you don't want to be able to edit content.