Update cross-tenant-access.md#2872
Conversation
Added a note about the -Verbose flag to help guests debug API calls.
|
@caydenwelter : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 3431ec2: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Pull request overview
Updates the cross-tenant access for guests documentation to make the PowerShell guidance easier to troubleshoot and to standardize parameter punctuation in the sample commands.
Changes:
- Adds a note about using PowerShell’s
-Verboseoutput to help diagnose REST API calls. - Replaces en-dash characters with standard hyphens in
Invoke-PowerBIRestMethodparameter flags.
| $body = ‘{ “resourceTenantObjectId”: “GUID_VAL” }’ | ||
| $url = “https://api.powerbi.com/v1/ephemeral/crosstenantauth/revokeConsent” | ||
| Invoke-PowerBIRestMethod -Url $url -Method Put –Body $body –ContentType “application/json” | ||
| Invoke-PowerBIRestMethod -Url $url -Method Put -Body $body -ContentType “application/json” |
There was a problem hiding this comment.
The PowerShell snippet uses typographic (curly) quotes around strings/JSON (for example, in $body, $url, and -ContentType). These characters will cause copy/paste execution failures in PowerShell; use straight ASCII quotes consistently (matching the earlier snippet).
| ## Enable cross tenant access | ||
|
|
||
| This section shows how to enable cross tenant access using PowerShell scripts that call Fabric REST APIs. You can use other methods to call these APIs. | ||
| This section shows how to enable cross tenant access using PowerShell scripts that call Fabric REST APIs. You can use other methods to call these APIs. You can append `-Verbose` to surface additional diagnostic output during execution. |
There was a problem hiding this comment.
This new sentence adds another instance of "cross tenant" without a hyphen. The article title/front matter already uses "cross-tenant"; consider using "cross-tenant" consistently here (and in the heading) to match the established term.
| ## Disable cross tenant access | ||
|
|
||
| This section shows how to disable cross tenant access using PowerShell scripts that call Fabric REST APIs. You can use other methods to call these APIs. | ||
| This section shows how to disable cross tenant access using PowerShell scripts that call Fabric REST APIs. You can use other methods to call these APIs. You can append `-Verbose` to surface additional diagnostic output during execution. |
There was a problem hiding this comment.
This new sentence adds another instance of "cross tenant" without a hyphen. The article title/front matter already uses "cross-tenant"; consider using "cross-tenant" consistently here (and in the heading) to match the established term.
Added a note about the -Verbose flag to help guests debug API calls.
Also conformed "–" versus "-" in the PowerShell parameters.
Thank you for contributing to Microsoft Fabric documentation
Fill out these items before submitting your pull request:
If you are working internally at Microsoft:
Provide a link to an Azure DevOps Boards work item that tracks this feature/update.
Who is your primary Skilling team contact? @mention them individually tag them and let them review the PR before signing off.
For internal Microsoft contributors, check off these quality control items as you go
1. Check the Acrolinx report: Make sure your Acrolinx Total score is above 80 minimum (higher is better) and with no spelling issues. Acrolinx ensures we are providing consistent terminology and using an appropriate voice and tone, and helps with localization.
2. Successful build with no warnings or suggestions: Review the build status to make sure all files are green (Succeeded).
3. Preview the pages:: Click each Preview URL link to view the rendered HTML pages on the review.learn.microsoft.com site to check the formatting and alignment of the page. Scan the page for overall formatting, and look at the parts you edited in detail.
4. Check the Table of Contents: If you are adding a new markdown file, make sure it is linked from the table of contents.
5. #sign-off to request PR review and merge: Once the pull request is finalized and ready to be merged, indicate so by typing
#sign-offin a new comment in the Pull Request. If you need to cancel that sign-off, type#hold-offinstead. Signing off means the document can be published at any time. Note, this is a formatting and standards review, not a technical review.Merge and publish
#sign-off, there is a separate PR Review team that will review the PR and describe any necessary feedback before merging.#sign-offagain. The PR Review team reviews and merges the pull request into the specified branch (usually the main branch or a release- branch).