updated links.

Author: AbdullahBell

articles/ddos-protection/ddos-optimization-guide.md

@@ -31,7 +31,7 @@ Cost optimization for DDoS protection requires understanding your risk profile a
 | **Develop a comprehensive asset inventory** that catalogs all public IP addresses and their business criticality levels. | A complete inventory enables risk-based protection decisions and prevents both over-provisioning expensive protection and leaving critical assets unprotected. You can prioritize protection investments based on actual business impact. |
 | **Establish clear accountability** for protection decisions with defined roles for security, operations, and finance teams. | Clear accountability ensures protection decisions consider both security requirements and budget constraints. Collaborative decision-making prevents siloed choices that might compromise security or exceed budgets. |
 | **Create realistic budgets** that account for both immediate protection needs and planned growth in public-facing resources. | Proper budgeting enables predictable protection costs and prevents reactive decisions during security incidents. You can plan protection expansion as your infrastructure grows. |
-| **Implement [risk assessment frameworks](/azure/cloud-adoption-framework/govern/security-baseline/risk-tolerance)** that define minimum protection levels and standardized policies for different asset types. | Risk-based frameworks provide structured approaches to evaluate DDoS attack risks while ensuring consistent protection decisions. They help identify critical assets, assess vulnerabilities, and determine appropriate protection measures based on business impact and risk tolerance, preventing both under-protection of critical assets and over-protection of low-risk resources. |
+| **Implement [risk assessment frameworks](/azure/cloud-adoption-framework/govern/security-baseline/assess-cloud-risks)** that define minimum protection levels and standardized policies for different asset types. | Risk-based frameworks provide structured approaches to evaluate DDoS attack risks while ensuring consistent protection decisions. They help identify critical assets, assess vulnerabilities, and determine appropriate protection measures based on business impact and risk tolerance, preventing both under-protection of critical assets and over-protection of low-risk resources. |
 
 ## Choose the right protection model
 
@@ -51,7 +51,7 @@ Optimize your architecture to reduce the number of public IP addresses requiring
 |---|---|
 | **Consolidate public-facing services** behind [Azure Load Balancer](/azure/load-balancer/) or [Application Gateway](/azure/application-gateway/) to reduce the total number of public IP addresses. | Fewer public IP addresses require protection, directly reducing expenses. Consolidation also improves security by reducing attack surface and simplifies protection management. |
 | **Use network segmentation such as [Azure Private Link](/azure/private-link/) and [virtual network peering](/azure/virtual-network/virtual-network-peering-overview)** to separate public-facing and internal resources. | You can focus protection spending on genuinely public-facing resources while using private connectivity for internal communications. This eliminates DDoS protection needs on internal paths, reducing costs while improving security. |
-| **Design application architecture** to minimize direct public IP exposure through proper use of [reverse proxies](/azure/architecture/patterns/reverse-proxy) and [content delivery networks](/azure/cdn/). | Architectural efficiency reduces the protection scope and associated costs. You can often protect an entire application through a single or few public endpoints rather than exposing multiple services directly. |
+| **Design application architecture** to minimize direct public IP exposure through proper use of [load balancing](/azure/architecture/guide/technology-choices/load-balancing-overview) and [content delivery networks](/azure/cdn/). | Architectural efficiency reduces the protection scope and associated costs. You can often protect an entire application through a single or few public endpoints rather than exposing multiple services directly. |
 
 ## Optimize resource utilization
 
@@ -68,7 +68,7 @@ Protection needs change as your infrastructure evolves. Set up continuous monito
 
 | Recommendation | Benefit |
 |---|---|
-| **Set up cost alerts** when DDoS protection spending approaches predefined budget thresholds. | Proactive notifications prevent budget overruns and enable timely adjustments to protection strategy. You can respond to cost increases before they impact other initiatives. To create cost alerts, see [Monitor usage and spending with cost alerts in Cost Management](/azure/cost-management-billing/costs/cost-mgt-alerts-monitor-usage-spending.md). |
+| **Set up cost alerts** when DDoS protection spending approaches predefined budget thresholds. | Proactive notifications prevent budget overruns and enable timely adjustments to protection strategy. You can respond to cost increases before they impact other initiatives. To create cost alerts, see [Monitor usage and spending with cost alerts in Cost Management](/azure/cost-management-billing/costs/cost-mgt-alerts-monitor-usage-spending). |
 | **Conduct quarterly reviews** of protected resources and their business criticality to identify optimization opportunities. | Regular reviews ensure protection investments remain aligned with business priorities. You can identify resources that no longer need protection or require upgraded protection based on changing importance. |
 | **Monitor attack patterns** and protection effectiveness to optimize coverage decisions. [View alerts in Microsoft Defender for Cloud](ddos-view-alerts-defender-for-cloud.md) and utilize [DDoS Protection logs in Log Analytics workspace](ddos-view-diagnostic-logs.md). | Understanding actual threat patterns enables data-driven protection decisions. You can adjust protection levels based on real attack data rather than theoretical risks. |
 | **Track protection ROI and implement lifecycle management** using [cost management best practices](/azure/cost-management-billing/costs/cost-analysis-common-uses) to measure value and decommission unnecessary protection. | ROI measurement demonstrates protection value and guides future investment decisions. Regular cleanup of inactive or non-critical resources prevents spending growth that doesn't align with business value while freeing budget for higher-priority resources. |