Scope outdated?
The scope for Databricks access described here seems to be no longer valid:
"error_description": "AADSTS1002012: The provided value for scope 2ff814a6-3304-4ab8-85cb-cd0e6f879c1d%2F.default is not valid.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 34a79d78-8f67-ee0d-71cc-bd34624c674f
- Version Independent ID: d993ef52-99c6-0d3c-6d4e-6d84b6c43125
- Content: Get Azure AD tokens for service principals - Azure Databricks
- Content Source: databricks/dev-tools/api/latest/aad/service-prin-aad-token.md
- Service: azure-databricks
- GitHub Login: @mssaperla
- Microsoft Alias: saperla
@kasuteru
Thanks for your feedback! We will investigate and update as appropriate.
I could have been more precise. There is an ongoing issue that this command simply does not work with cURL (I am not the only one - check the number of requests on Google - lots of people have that problem: https://www.google.com/search?q=following+parameter%3A+grant+type+900144&rlz=1C1GCEB_enDE1018DE1018&oq=following+parameter%3A+grant+type+900144&aqs=chrome..69i57j69i60.7287j0j7&sourceid=chrome&ie=UTF-8)
When trying to run it with Postman (and maybe with cURL as well, I haven't gotten so far yet), the scope needs to be replaced with an actual / instead of the encoding:
Docs example:

What actually works in postman:

@kasuteru
I've delegated this to content author @mssaperla to review and share his valuable insights.
Thanks for your dedication to our documentation. Unfortunately, we have been unable to review your issue and apologize for the delayed response. The requested updates have not yet been made. The timeline for resolution varies based on resourcing. We've created an internal work item (DOC-7752) to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close