Adding Warning section about Secure by Default #127226
Conversation
Adding the following warning section so that customers know that making this upgrade does then require an NSG associated to the Interface: Be aware that Standard SKU IP Addresses are considered Secure by default and will be closed to all internal traffic. It is recommended to apply an NSG to the Subnet or Network Interface that the Public IP address is assoicated in order to prevent unexpected downtime, see Public IP addresses in Azure
prmerger-automator
bot
requested review from
mbender-ms,
cherylmc and
AbdullahBell
|
@magilbe : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 3091538:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/virtual-network/ip-services/public-ip-upgrade.md | Details |
articles/virtual-network/ip-services/public-ip-upgrade.md
- Line 24, Column 275: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-addresses#sku' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 24, Column 275: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-addresses#sku' will be broken in isolated environments. Replace with a relative link.
For more details, please refer to the build 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.
| @@ -20,6 +20,9 @@ Azure public IP addresses are created with a SKU, either Basic or Standard. The | |||
|
|
|||
| In this article, you learn how to upgrade a static Basic SKU public IP address to Standard SKU in the Azure portal, Azure CLI, or Azure PowerShell. | |||
|
|
|||
| > [!WARNING] | |||
| > Be aware that Standard SKU IP Addresses are considered Secure by default and will be closed to all internal traffic. It is recommended to apply an NSG to the Subnet or Network Interface that the Public IP address is assoicated in order to prevent unexpected downtime, see [Public IP addresses in Azure](https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-addresses#sku) | |||
There was a problem hiding this comment.
| > Be aware that Standard SKU IP Addresses are considered Secure by default and will be closed to all internal traffic. It is recommended to apply an NSG to the Subnet or Network Interface that the Public IP address is assoicated in order to prevent unexpected downtime, see [Public IP addresses in Azure](https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-addresses#sku) | |
| > Be aware that Standard SKU IP Addresses are considered Secure by default and will be closed to all internal traffic. It is recommended to apply an NSG to the Subnet or Network Interface that the Public IP address is assoicated in order to prevent unexpected downtime, see [Public IP addresses in Azure](https://learn.microsoft.com/azure/virtual-network/ip-services/public-ip-addresses#sku) |
fixing build error
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
|
Yes looks good! #sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @mbender-ms |
|
Hi @magilbe - Thanks for your review. In the public repo, pull requests should be signed off by the author, another member of the content team, or a PM. @mbender-ms Could you take a look? Thanks! |
Adding the following warning section so that customers know that making this upgrade does then require an NSG associated to the Interface:
Be aware that Standard SKU IP Addresses are considered Secure by default and will be closed to all internal traffic. It is recommended to apply an NSG to the Subnet or Network Interface that the Public IP address is assoicated in order to prevent unexpected downtime, see Public IP addresses in Azure