Hard to follow because some outdated information

[kaysauter]

Hi,

unfortunately, this article is very hard and cumbersome to follow, for a couple of reasons:

• Structuring isn't very good sometimes. In some numbered paragraphs, more than one step is explained, but in most, each step gets their own paragraph and number.
• "then select Add dynamic content" is not really clear at first, because I was lookig for a button at first. I had a quite while until i realized there's a text link appearing. A picture to explain what that is meant would have been great.
• ". Copy and paste the GET request that has been parameterized using the @concat string function below into the dynamic content box." and the actual box that should be copied follows in the second box. Because the first box also has parameters, it takes time to realize that it is really meant the second box. The text structure with indication to the actual box that needs be corrected should be directly under the text that points this out.
• "Select MSI as the Authentication type." The term "MSI" gets mentioned several times in this text, yet this radio button (now a dropdown-list) has changed. Also, "MSI" goes by a slightly different name and on top of that, not as abbreviation.
• Most of the screenshots are outdated.
• Why is eg. https://management.azure.com/ as inline-text and not in a code box from which you can copy? If something is meant to be copied, then be consistent and use code-boxes for all such things or then inline text.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 239e657e-15d8-05a3-466d-4159b178307e
• Version Independent ID: 866f6f93-0302-324b-668e-b41f67581d6d
• Content: How to pause and resume dedicated SQL pools with Synapse Pipelines - Azure Synapse Analytics
• Content Source: articles/synapse-analytics/sql/how-to-pause-resume-pipelines.md
• Service: synapse-analytics
• Sub-service: sql
• GitHub Login: @kromerm
• Microsoft Alias: makromer

[SaibabaBalapur-MSFT]

@kaysauter Thanks for your feedback! We will investigate and update as appropriate.

[RamanathanChinnappan-MSFT]

@kaysauter I've delegated this to @kromerm, a content author, to review and share their valuable insights.

[bandersmsft]

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close