Update dev tunnel instuctions per request

[yyw-msft]

No description provided.

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit ef2f075:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-node.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[ShannonLeavitt]

@anujb-msft

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

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

[yyw-msft]

@anujb-msft , can u help me review this short pr?

[Court72]

@anujb-msft

Can you review this old PR and determine whether it needs to be closed or merged?

[American-Dipper]

PR review team emailed the author today

[learn-build-service-prod]

Learn Build status updates of commit 678fca1:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-node.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@jutik0

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

[learn-build-service-prod]

Learn Build status updates of commit 0d7710d:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/communication-services/quickstarts/call-automation/includes/quickstart-make-an-outbound-call-using-callautomation-node.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Stacyrch140]

@jutik0

Can you review the proposed changes or confirm whether this PR needs to be closed?

[denrea]

@anujb-msft

Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

[ttorble]

Sent email to @anujb-msft today.

[Court72]

I sent an email to @jutik0 today.

[ShannonLeavitt]

@williamzhao87 - I see that you have recently modified this file. Can you review this PR and sign off if you approve?

[ttorble]

I sent email to @williamzhao87 today.

@MicrosoftDocs/public-repo-pr-review-team

[ttorble]

Sent email to @jutik0 and @williamzhao87 today.

@MicrosoftDocs/public-repo-pr-review-team

[ttorble]

@yyw-msft

It looks like you have access to the private repo azure-docs-pr where you can sign off on your own PRs. If this content change is still needed, can you close this PR and open a new one in the private repo?

Thanks

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

@jutik0

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

[v-dirichards]

I sent a Teams message to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team