Update from SAP DITA CMS (squashed):

commit 8ee9bfdae520b97284ab6417996ff2e4f32693aa
Author: REDACTED
Date:   Mon Mar 24 13:00:42 2025 +0000

    Update from SAP DITA CMS 2025-03-24 13:00:42

    Project: dita-all/nbu1622790870513
    Project map: 16e6d8e0d7bf422c82818b7625b724b0.ditamap
    Output: loioc337387b1cd14803bda2ccf11484b81b
    Language: en-US
    Builddable map: ecbe88a694f54c599a95fc3b96a803d7.ditamap

commit 2da53ba7f6503f6cdfac1cb97b0fe12b4aafe993
Author: REDACTED
Date:   Mon Mar 24 08:57:46 2025 +0000

    Update from SAP DITA CMS 2025-03-24 08:57:46

    Project: dita-all/nbu1622790870513
    Project map: 16e6d8e0d7bf422c82818b7625b724b0.ditamap
    Output: loioc337387b1cd14803bda2ccf11484b81b
    Language: en-US
    Builddable map: ecbe88a694f54c599a95fc3b96a803d7.ditamap

commit 112acaa58b14177d960373078973381b7fce4f66
Merge: 3801123 123b7b3
Author: REDACTED
Date:   Wed Mar 19 16:48:44 2025 +0100

    Merge pull request #11 from UACP/reuse-fix

    Reuse Version update from dep to toml

##################################################
[Remaining squash message was removed before commit...]

Author: ditaccms-bot

docs/configure-dns-on-kyma-72a3646.md

@@ -18,7 +18,7 @@
 
 ## Overview
 
-The last step of connecting SAP Private Link Service is the binding of the application to a service instance. As a result of the creation of a binding between you application and a private link service instance, a secret that contains the binding credentials is created. That secret contains information about the private link endpoint in the form of FQDN and internal \(private\) IP address. There are various options in configuring the kyma cluster DNS so that the internal IP address is resolved from the FQDN.
+The last step of connecting SAP Private Link Service is the binding of the application to a service instance. As a result of the creation of a binding between you application and a Private Link Service instance, a secret that contains the binding credentials is created. That secret contains information about the private link endpoint in the form of FQDN and internal \(private\) IP address. There are various options in configuring the Kyma cluster DNS so that the internal IP address is resolved from the FQDN.
 
 
 

docs/css/BusinessSuiteInAppSymbols-V2.woff

@@ -6,8 +6,8 @@
 @font-face{font-family:'bwicons';src: url('./bwicons.ttf') format('truetype');font-weight: normal;font-style: normal;}
 @font-face{font-family:'FPA-icons';src: url('./FPA-icons.woff') format('woff');font-weight: normal;font-style: normal;}
 @font-face{font-family:'FPA-icons-V2';src: url('./FPA-icons-V2.woff') format('woff');font-weight: normal;font-style: normal;}
-@font-face{font-family:'FPA-icons-V3';src: url('./font/FPA-icons-V3.woff') format('woff');font-weight: normal;font-style: normal;}
-@font-face{font-family:'ITOA_FontIcon';src: url('./ITOA_FontIcon.eot');src: url('./ITOA_FontIcon.eot?#iefix') format('embedded-opentype'),url('./ITOA_FontIcon.ttf') format('truetype');font-weight: normal;font-style: normal;}
+@font-face{font-family:'FPA-icons-V3';src: url('./FPA-icons-V3.woff') format('woff');font-weight: normal;font-style: normal;}
+@font-face{font-family:'ITOA_FontIcon';src: url('./ITOA_FontIcon.ttf') format('truetype');font-weight: normal;font-style: normal;}
 @font-face{font-family:'NS-SAP-icons';src: url('./NS-SAP-icons.woff') format('woff');font-weight: normal;font-style: normal;}
 @font-face{font-family:'NS-SAP-icons-extended';src: url('./NS-SAP-icons-extended.woff') format('woff');font-weight: normal;font-style: normal;}
 @font-face{font-family:'sap-fiori-inapp-icons';src: url('./sap-fiori-inapp-icons.woff') format('woff');font-weight:normal;font-style:normal;}
@@ -27,6 +27,7 @@
 @font-face{font-family:'ve-icon-set';src: url('./ve-icon-set.woff') format('woff');font-weight:normal;font-style:normal;}
 @font-face{font-family:'FluentSystemIcons-Filled';src: url('./FluentSystemIcons-Filled.woff') format('woff');font-weight:normal;font-style:normal;}
 @font-face{font-family:'FluentSystemIcons-Regular';src: url('./FluentSystemIcons-Regular.woff') format('woff');font-weight:normal;font-style:normal;}
+@font-face {font-family:'EmarsysHorizon';src: url('./EmarsysHorizon.woff') format('woff');font-weight: normal;font-style: normal;}
 .Ariba-icons {font-family:Ariba_icon_library;}
 .Belize-icons {font-family:SAPGUI-Belize-Icons;}
 .BusinessSuiteInAppSymbols {font-family:BusinessSuiteInAppSymbols;}
@@ -55,4 +56,5 @@
 .sapsportsone {font-family:sapsportsone;}
 .ve-icon-set {font-family:ve-icon-set;}
 .FluentSystemIcons-Filled {font-family:FluentSystemIcons-Filled;}
-.FluentSystemIcons-Regular {font-family:FluentSystemIcons-Regular;}
+.FluentSystemIcons-Regular {font-family:FluentSystemIcons-Regular;}
+.EmarsysHorizon {font-family: EmarsysHorizon;}

docs/css/sap-icons.css

@@ -32,6 +32,9 @@ To privately access a service in your AWS accounts, SAP Private Link service cre
 
 See [Supported Services for Amazon Web Services in SAP BTP](supported-services-for-amazon-web-services-in-sap-btp-67e4c73.md), for all Amazon Web Services that can currently be consumed from SAP BTP.
 
+> ### Note:  
+> If you would like to use a service or scenario with SAP Private Link service that is not available yet, please open a support ticket on BC-CP-PRIVATELINK.
+
 
 
 <a name="loio575341947b854a82a9f3ba2bc6b1b6cc__section_kzz_tjs_45b"/>

docs/using-sap-private-link-service/consume-amazon-web-services-in-sap-btp-5753419.md

@@ -10,7 +10,7 @@ SAP Private Link service establishes a private connection between selected SAP B
 
 ## Overview
 
-To privately access a service in your Azure subcription, SAP Private Link service creates a private endpoint and reuses the private link functionality of Azure:
+To privately access a service in your Azure subscription, SAP Private Link service creates a private endpoint and reuses the private link functionality of Azure:
 
 ![Consuming Azure services in SAP BTP.](images/Private_Link_-_Scenario_1_0745a1a.png)
 
@@ -67,19 +67,6 @@ The following Azure services can currently be consumed from SAP BTP:
 > ### Note:  
 > If you would like to use a service or scenario with SAP Private Link service that is not available yet, please open a support ticket on BC-CP-PRIVATELINK.
 
-> ### Restriction:  
-> Mixing public and private endpoints for Azure resources in your Azure subscription when connected via SAP BTP using SAP Private Link, is not supported at this point.
-> 
-> Possible solutions to address such requirements are:
-> 
-> -   Use only private endpoints and add SAP Private Link service to your SAP BTP implementation.
-> 
-> -   Enable a mixed setup of private public access to the storage account via SAP BTP in parallel using Azure Application Gateway.
-> 
-> -   Use virtual hostname in the SAP Cloud Connector pointing to the internal IP of our Azure native service.
-> 
-> -   Remove the private endpoint on Azure and consume publicly.
-
 
 
 <a name="loioe9cc67716a3a41c9885862661e6c4234__section_zg3_cjz_cpb"/>

docs/using-sap-private-link-service/consume-azure-services-in-sap-btp-e9cc677.md

@@ -4,61 +4,8 @@
 
 SAP Private Link service lets you consume selected Azure native services of your Azure subscription in SAP BTP.
 
-
-
-<a name="loio3672119271fe4b319eaf3624870044b0__section_asm_51b_hdc"/>
-
-## Announcement
-
-
-
-<a name="loio3672119271fe4b319eaf3624870044b0__section_evm_pzg_hdc"/>
-
-## SAP Private link service keys will no longer contain the hostname of the connected resource, but instead the private IP address
-
-In order to remove the restrictions in [Consume Azure Services in SAP BTP](consume-azure-services-in-sap-btp-e9cc677.md), preventing customers to mix public and private endpoints for Azure resources in their Azure subscription when connected via SAP BTP using SAP Private Link, we plan to delete the SAP private link service managed Private DNS zones attached to the BTP Cloud Foundry regions.
-
-The following changes are to be expected:
-
--   SAP Private link service keys will no longer contain the hostname of the connected resource, but instead the private IP address. Due date is **January 2025**.
-
--   SAP managed Private DNS Zones to Azure native services will be deleted from the BTP Cloud Foundry regions. Due date is **March 31, 2025**.
-
-
-
-<a name="loio3672119271fe4b319eaf3624870044b0__section_fvm_pzg_hdc"/>
-
-## SAP managed Private DNS Zones to Azure native services will be deleted from the BTP Cloud Foundry regions
-
-Service keys credentials will no longer contain the hostname but only the private IP address of the provisioned private endpoint. This information can be used for testing the connection. If you want to consume the linked Azure/AWS resource over TLS \(thus using its private hostname\) you'll need to create a service binding to the consuming application and get the hostname information from the binding credentials. This would affect only service keys created after January 2025.
-
-
-
-As result DNS resolution of hostnames provisioned by SAP private link service will work in BTP Cloud Foundry environment only if the SAP private link service instance is bound to the consuming application. In order to prevent disruptions in your private link connectivity please check the **applicability criteria** to evaluate if you're affected, and if yes, make sure to go through the **Actions to take before March 31, 2025**.
-
-
-
-<a name="loio3672119271fe4b319eaf3624870044b0__section_u4q_5zg_hdc"/>
-
-## Applicability Criteria:
-
-
-
--   You have created instances of SAP Private link service in your SAP BTP cockpit accounts.
--   You use the SAP private link service instance to connect to one of the native services in [Consume Azure Services in SAP BTP](consume-azure-services-in-sap-btp-e9cc677.md), except for [Azure Private Link Service \(generic LB scenario for VMs and others\)](azure-private-link-service-generic-lb-scenario-for-vms-and-others-e8bc0c6.md).
--   You **have** created service keys in your SAP private link service instances **before January 2025**.
--   You**have not** created service bindings to consuming applications in your SAP Private link service instances.
-
-
-
-<a name="loio3672119271fe4b319eaf3624870044b0__section_mkf_wzg_hdc"/>
-
-## Actions to take:
-
-
-
--   Bind the SAP Private link service instances to the consuming applications.
-
+> ### Note:  
+> Service keys for SAP Private Link service instances in Cloud Foundry do not include the hostname of the connected resource, only the private IP address. While service keys can be used for testing purposes, it is recommended to use service bindings for production use.
 
 -   **[Consume Azure Services in SAP BTP](consume-azure-services-in-sap-btp-e9cc677.md "SAP Private Link service  establishes
 		a private connection between selected SAP BTP services and selected