APIMS fails provisioning with Private Endpoint set Statically allocate IP address.

[m-yuka746]

Hi team, I found the difference between the actual UI and docs UI image at Section Connect to a private endpoint, step 5.. Could you update it? I have attached the actual UI and docs image.

In addition, I have a question about Private IP configuration. When I create PE with setting Private IP configuration to Statically allocate IP address, I fail AMPLS provisioning after adding Azure Monitor resources. I understand that I can avoid the issue by creating PE with setting Private IP configuration to Dynamically allocate IP address. Is it expected issue? If so, could you add note about it or write that we should create PE with Dynamically allocate IP address?

Current UI (I mark changing points from docs image)

UI in docs.

---

Document Details

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

• ID: 2d8413ef-386c-50ee-8f72-2be280d10201
• Version Independent ID: ccd4143d-d5df-bb9f-5df4-80b049998473
• Content: Configure your Private Link - Azure Monitor
• Content Source: articles/azure-monitor/logs/private-link-configure.md
• Service: azure-monitor
• Sub-service: logs
• GitHub Login: @noakup
• Microsoft Alias: noakuper

[Naveenommi-MSFT]

@m-yuka746

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

[AnuragSingh-MSFT]

@m-yuka746, thank you for reporting it.

@noakup, could you please review this and share your thoughts. Thank you

[guywi-ms]

#reassign: @v-jbasden

@v-jbasden can you please update this image?

[v-jbasden]

Thanks for the feedback. The images have been updated.

#please-close

[m-yuka746]

@v-jbasden Thank you for updating. I have a question about [5. On the Virtual Network tab:]. When we set [Private IP configuration] to statically, AMPLS fails provisioning by adding Monitor resources. Should we set the setting to Dynamically?