Can you please correct the generic FQDNs with servicename-appname.az…
…uremicroservices.io
the eastus.azuremicroservices is misleading opening this based on Asir's suggestion. Example: https://srramspring1-customers-service.azuremicroservices.io/owners
@sramayanam : Thanks for your contribution! The author(s) have been notified to review your proposed change.
Learn Build status updates of commit 0c544bf:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/spring-apps/how-to-integrate-azure-load-balancers.md | :warning:Warning | Details |
articles/spring-apps/how-to-integrate-azure-load-balancers.md
- Line 73, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link 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:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
@KarlErickson
Can you address @sramayanam's comment and make the appropriate changes?
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
@sramayanam could you please update your pull request to show the specific change you'd like to see? Currently, your feedback comment is embedded in the doc as a proposed change, and I'm not sure what you are looking for specifically. Alternatively, you can close this pull request and open an issue instead, and then explain the problem in more detail. Then, a subject matter expert can take a look and create a pull request to update the doc. Thanks!
@hangwan97 @selvasingh can you take a look and indicate the specific change required? Thanks!
Ping. @hangwan97 @selvasingh can you take a look and indicate the specific change required? Thanks!
This PR seems to be an issue request, please do raise an issue so that we go follow up with the next steps.
@sramayanam if this is still a problem, please file an issue or discuss this with @hangwan97 internally. Thanks!
#please-close