In the left pane of the new SharePoint admin center, under Policies, select Access control Idle session sign-out.
You can define the auto sign-out from minutes until a day, but the pop-up notification can only be set from a minute to half-hour, and the behavior is that you will receive the pop-up after that much idle time and not when you have that time as remaining, which means that you can set as your users will be disconnected in a day, and will receive the pop-up for every idle minute, which doesn't make any sense.
My request is to have the pop-up to appear as a remaining to be disconnected and not to appear after so little idle time.

Hi,

I wasnt sure where to report this. But my client uses short acronyms for the sharepoint team sites. One in particular was a site called "Contruction", easiest short name would be "con", so we happily created a team site called "con". However, it doesnt create the SharePoint URL with "con" in it, instead it opts for a random string. We thought maybe the build process was broken, so opted to rebuild one with "contruct" and it went through fine, i.e. it created the SP team site with the correct path.

Are there some reserved words we cannot use with SharePoint URLS? If so they should probably be blocked when creating the sites from the front-end?

Here is what the Active Sites listing shows, ive tried this twice with the same result.

Site Name URL
con ../sites/4mxa9k6fbfku1h0
construct ../sites/construct

The method from this documentation : https://docs.microsoft.com/en-us/sharepoint/administration/move-or-rename-service-application-databases#steps-to-move-or-rename-the-search-service-application-databases
are not working for SharePoint Server 2019. Instead you should use this methid :
1. Restore Search Service Application from Search Admin DB
2. Suspend the Search Service
3.Associate the Search Administration Database
4.Associate the Search Analytics Reporting Database
5.Associate the Search Crawl Store Database
6.Associate the Search Links Store Database
7.Suspend the Search Service
Use this PS Script :
<########################################################################################################
This script intend to change the SharePoint 2019 Search Service Application Databases names
Description : The formal process from older sharepoint versions not applicable for SharePoint 2019,
Use this script to rename the databases name
This Script assume you allready restore the search administration database
Author : Ron Ness (Microsoft)
Date : August,25 2019
#########################################################################################################>

#Add SharePoint *.DLLs if needed
if ((Get-PSSnapin "Microsoft.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null){
Add-PSSnapin *SharePoint*
}

<#===============================================================================================================================
Step 1 Suspend the Search Service :
1.On the Start menu, click All Programs.
2.Click Microsoft SharePoint Products.
3.Click SharePoint Management Shell.
4.In the SharePoint Management Shell, enter the following Windows PowerShell statement to suspend the search service:
=================================================================================================================================#>
$searchServiceApplicationName = "<Search Service Application Name>"
$ssa = Get-SPEnterpriseSearchServiceApplication $searchServiceApplicationName
Suspend-SPEnterpriseSearchServiceApplication -Identity $ssa

<#===============================================================================================================================
Step 2 Associate the Search Administration Database :
1.On the Start menu, click All Programs.
2.Click Microsoft SharePoint Products.
3.Click SharePoint Management Shell.
4.In the SharePoint Management Shell, enter the following Windows PowerShell statement to associate the new Search
Administration database with the Search Service Application:

* Please note that if you have restored Search Administration DB you can continue to the next step (3)
=================================================================================================================================#>
#$ssa = Get-SPEnterpriseSearchServiceApplication $searchServiceApplicationName
#$ssa | Set-SPEnterpriseSearchServiceApplication -DatabaseName SP_Search -DatabaseServer SQLSP19SRV

<#===============================================================================================================================
Step 3 Associate the Search Analytics Reporting Database :
1.On the Start menu, click All Programs.
2.Click Microsoft SharePoint Products.
3.Click SharePoint Management Shell.
4.In the SharePoint Management Shell, enter the following Windows PowerShell statement to associate the new Analytics Reporting
database with the Search Service Application:
=================================================================================================================================#>
Add-SPServerScaleOutDatabase -ServiceApplication $ssa -DatabaseServer SQLSP19SRv -DatabaseName SP_AnalyticsReportingDB #if you get an error that the database allready exist you will need to remove row object from 'SharePoint_Config' DB : Delete From Objects where Name = 'Database Name';
$temp = Get-SPServerScaleOutDatabase -ServiceApplication $ssa
Remove-SPServerScaleOutDatabase -ServiceApplication $ssa -Database $temp[0]

<#===============================================================================================================================
Step 4 Associate the Search Crawl Store Database :
1.On the Start menu, click All Programs.
2.Click Microsoft SharePoint Products.
3.Click SharePoint Management Shell.
4.In the SharePoint Management Shell, enter the following Windows PowerShell statement to associate the new Crawl Store
Database with the Search Service Application:
=================================================================================================================================#>
New-SPEnterpriseSearchCrawlDatabase -SearchApplication $ssa -DatabaseName SP_CrawlStoreDB -DatabaseServer SQLSP19SRV #Create new Crawl Store Database
$crawlDBToDelete = $ssa | Get-SPEnterpriseSearchCrawlDatabase -Identity "<Old Crawl Store Database>"
Remove-SPEnterpriseSearchCrawlDatabase -Identity $crawlDBToDelete
#Optional for viewing details
$CrawlDatabase0 = ([array]($ssa | Get-SPEnterpriseSearchCrawlDatabase))[0]
#Please Note : the below command doesn't works on SharePoint 2019
#$CrawlDatabase0 | Set-SPEnterpriseSearchCrawlDatabase -DatabaseName SP_CrawlStoreDB -DatabaseServer SQLSP19SRV

<#===============================================================================================================================
Step 5 Associate the Search Links Store Database :
1.On the Start menu, click All Programs.
2.Click Microsoft SharePoint Products.
3.Click SharePoint Management Shell.
4.In the SharePoint Management Shell, enter the following Windows PowerShell statement to associate the new Links Store
Database with the Search Service Application:
=================================================================================================================================#>
New-SPEnterpriseSearchLinksDatabase -DatabaseName SP_LinksStoreDB –SearchApplication $ssa -DatabaseServer SQLSP19SRV # Create new Links Store Database

$oldLinksStoreDB = ([array]($ssa | Get-SPEnterpriseSearchLinksDatabase))[0] # Get Old Links Store Database Identity (Run this command :'$ssa | Get-SPEnterpriseSearchLinksDatabase' to ensure this is the right Database)
$newLinksStoreDB = ([array]($ssa | Get-SPEnterpriseSearchLinksDatabase))[1] # Get New Links Store Database Identity (Run this command :'$ssa | Get-SPEnterpriseSearchLinksDatabase' to ensure this is the right Database)
Move-SPEnterpriseSearchLinksDatabases -SearchApplication $ssa -TargetStores @($newLinksStoreDB) -Confirm:$false

Resume-SPEnterpriseSearchServiceApplication -Identity $ssa #Resume the Search Service Application, Without resuming the the search service application you won't be able to remove the old Links Store Database

Remove-SPEnterpriseSearchLinksDatabase -Identity $oldLinksStoreDB -SearchApplication $ssa -Confirm:$false
#Please Note : the below command doesn't works on SharePoint 2019
#$LinksDatabase0 | Set-SPEnterpriseSearchLinksDatabase -DatabaseName SP_LinksStoreDB -DatabaseServer SQLSP19SRV -SearchApplication $ssa

We have observed that there are a few actions with respect to SharePoint Online, which when performed (either via SPO admin center or PowerShell) doesn't generate any event in Audit logs. Here is a list of such actions:
UI
-------------
SharePoint Admin Center->Settings->Custom Script
SharePoint Admin Center->Settings->Connected Services->Block SharePoint 2013 Workflows

PowerShell
--------------
PS> Set-SPOTenant -DisabledWebPartIds
PS> Set-SPOTenant -DisallowInfectedFileDownload
PS> Set-SPOTenant -ExternalServicesEnabled
PS> Set-SPOTenant -NoAccessRedirectUrl
PS> Set-SPOTenant -ODBAccessRequests
PS> Set-SPOTenant -ODBMembersCanShare
PS> Set-SPOTenant -OfficeClientADALDisabled
PS> Set-SPOTenant -OwnerAnonymousNotification
PS> Set-SPOTenant -UsePersistentCookiesForExplorerView
PS> Set-SPOTenant -UserVoiceForFeedbackEnabled
PS> Set-SPOTenantSyncClientRestriction -DisableReportProblemDialog

Could you please look into this and provide any inputs as we need to track these actions?

Thanks, Paresh

Currently when a user requests access ("I'd like access") the Request For field holds the site address and not the address of the specific item that the user was attempting to open when they encountered the "access denied" screen. Users are generally not trying to access the entire site (they have View permissions to much of the content) but specific resources.

As it is, admins need to message the user to work out what exactly they were trying to use. On a site where different resources are accessible to different user groups, this is really unhelpful and creates work for admins and frustration for users.

The access request should relate to the specific item that the user wishes to open or modify, and not to the entire site. This will make it possible to grant the appropriate permission on that item only while keeping least privileges on the containing site.