Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSS-Networking: Bastion Document Update troubleshoot.md #125477

Merged
merged 2 commits into from
Feb 24, 2025

Conversation

SamekshaPandhiMS
Copy link
Contributor

This document https://learn.microsoft.com/en-us/azure/bastion/troubleshoot#filetransfer need to be updated as content "File transfer isn't supported at this time. We're working on adding support." is outdated now. We support file transfer for bastion and its mentioned correctly in other doc https://learn.microsoft.com/en-us/azure/bastion/bastion-faq#file-transfer.

So here we need to replace this
"File transfer isn't supported at this time. We're working on adding support."
with this
"Azure Bastion offers support for file transfer between your target VM and local computer using Bastion and a native RDP or SSH client. At this time, you can’t upload or download files using PowerShell or via the Azure portal. For more information, see Upload and download files using the native client."

Document URL (needs to be updated) - https://learn.microsoft.com/en-us/azure/bastion/troubleshoot#filetransfer

Document URL (already updated) - https://learn.microsoft.com/en-us/azure/bastion/bastion-faq#file-transfer

This document https://learn.microsoft.com/en-us/azure/bastion/troubleshoot#filetransfer need to be updated as content "File transfer isn't supported at this time. We're working on adding support." is outdated now. We support file transfer for bastion and its mentioned correctly in other doc https://learn.microsoft.com/en-us/azure/bastion/bastion-faq#file-transfer.

So here we need to replace this 
"File transfer isn't supported at this time. We're working on adding support." 
with this 
"Azure Bastion offers support for file transfer between your target VM and local computer using Bastion and a native RDP or SSH client. At this time, you can’t upload or download files using PowerShell or via the Azure portal. For more information, see Upload and download files using the native client."
Copy link
Contributor

@SamekshaPandhiMS : Thanks for your contribution! The author(s) have been notified to review your proposed change. @isamorris

Copy link
Contributor

Learn Build status updates of commit 9b8ef5d:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/bastion/troubleshoot.md ⚠️Warning Details

articles/bastion/troubleshoot.md

  • Line 85, Column 260: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/azure/bastion/vm-upload-download-native' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
  • Line 85, Column 260: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/azure/bastion/vm-upload-download-native' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

@SamekshaPandhiMS
Copy link
Contributor Author

#sign-off

Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @isamorris

@v-dirichards
Copy link
Contributor

v-dirichards commented Jan 9, 2025

Hi @SamekshaPandhiMS - Thanks for your review. In the public repo, pull requests should be signed off by the author, another member of the content team, or a PM.

@isamorris -- Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Jan 9, 2025
@SamekshaPandhiMS
Copy link
Contributor Author

SamekshaPandhiMS commented Jan 10, 2025 via email

@isamorris99
Copy link
Contributor

looks good thanks!

@isamorris99
Copy link
Contributor

#sign-off

Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @isamorris

Copy link
Contributor

Learn Build status updates of commit 0f98f79:

✅ Validation status: passed

File Status Preview URL Details
articles/bastion/troubleshoot.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@ttorble
Copy link
Contributor

ttorble commented Feb 24, 2025

@isamorris99 Could you update the author metadata to match your GitHub alias in a PR in the private repo please? (So that you can sign off on PRs in the public repo.) Thanks

@ttorble ttorble merged commit c7c6d3e into MicrosoftDocs:main Feb 24, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants