Closed JohnPoetzinger closed 5 months ago
@JohnPoetzinger Thanks for your feedback! We will investigate and update as appropriate.
Thanks for your dedication to our documentation. This issue has been moved to an internal work item for triage and prioritization. Thanks in advance for your understanding as we investigate to provide the most accurate documentation updates. #please-close
Internal work item: https://dev.azure.com/msft-skilling/Content/_workitems/edit/262450
Please also note that GitHub documentation issues are being phased out completely. For more information see: https://aka.ms/ContentUserFeedback.
Our support team is available to assist you if you have any pressing questions or problems that need to be resolved. You can create a support ticket by visiting the following link: https://azure.microsoft.com/support/create-ticket/
You may also ask support questions to our Q&A forums or on Stack Overflow when the questions are related to coding.
Subnet Planning provides minimum subnet size but needs additional information to plan the appropriate size of the subnet for production deployments. A Lengthy engagement with support got me this info:
Monitor Resource Type | IPs needed for first instance to connect with AMPLS | IPs needed for each additional instance to connect with AMPLS Application Insights | Up to 10 | Up to 2 Data Collection Rules | Up to 11 | Up to 3 Log Analytics Workspace | Up to 11 | Up to 3
Please validate and include this IP table so users can plan their address space for their deployments.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.