Skip to content

Conversation

anjalidivitha
Copy link
Contributor

Added a clarification under URL template requirements stating that the full API URL must be less than 128 characters long. This update aligns with existing backend constraints and helps users avoid import failures due to overly long URLs.

Error Details:
image

Copy link
Contributor

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

Copy link
Contributor

Learn Build status updates of commit 1aa3ff3:

✅ Validation status: passed

File Status Preview URL Details
articles/api-management/api-management-api-import-restrictions.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-dirichards
Copy link
Contributor

@dlepow

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 Apr 16, 2025
@v-dirichards
Copy link
Contributor

I sent an email to the content owner today.

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

@v-dirichards
Copy link
Contributor

@dlepow

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

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

@v-dirichards
Copy link
Contributor

I sent a Teams message to the content owner today.

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

@ttorble
Copy link
Contributor

ttorble commented Aug 14, 2025

I sent email to the content owner today.

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

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