Retrieve SharePoint Site ID from URL/Path Using Graph API Without Sites.Read.All Permission

Is your feature request related to a problem? Please describe the problem.

Hi,

My Java application integrates with SharePoint using the Microsoft Graph API Java SDK to upload and download files from document libraries.

The end-user workflow is as follows:

1. Select a SharePoint site from a list, or provide the relative site path (URL).
2. Select a document library from the chosen site (we list all available libraries).
3. Use a file browser to navigate through the contents and upload/download files or folders.

We’ve noticed that in step #1, listing available sites requires the Sites.Read.All or Sites.ReadWrite.All permissions. Even when trying to retrieve a Site ID from a known path, it requires one of these broad permissions.

However, many of our customers are unwilling to grant Sites.Read.All to our application due to its wide scope.
We would like to know if there is a way (via the API) to:

• list only the sites our app has access to through Sites.Selected?
• retrieve a Site ID using its name, URL, or relative path without needing Sites.Read.All?

Ideally, our app should be able to query only the sites explicitly granted through Sites.Selected, and retrieve the Site ID using a known path.

If this is currently not supported, could you please consider this feature? This capability would be very helpful, especially since many users find it challenging to manually extract the Site ID using browser requests like /api/site/id.

Thanks,
Avner

Describe the solution you'd like.

• Retrieve the site ID from the relative Path
  and/or
• Allow the existing list sites API to treat the Sites.Selected (rather than Sites.Read.All) permissions.

Additional context?

No response

Start by reviewing the Microsoft Graph API Java SDK entry points for listing sites and retrieving a site ID by name, URL, or relative path, along with the Sites.Selected permission behavior described here. Done would mean establishing whether these operations can be supported without Sites.Read.All and, if so, defining the requested API behavior and validating it with appropriate SDK coverage.