diff --git a/wpf-toc.html b/wpf-toc.html
index ce9b7e92f..fa7682486 100644
--- a/wpf-toc.html
+++ b/wpf-toc.html
@@ -47,11 +47,10 @@
Overview
How to Generate Syncfusion WPF License Key?
How to Register Syncfusion License Key in WPF Application?
- How to Validate Syncfusion License Key In CI Services?
+ How to Validate Syncfusion License Key In CI Services?
Licensing Errors
Licensing FAQ
- - How to Validate Syncfusion License Key In CI Services?
- Is an internet connection required for Syncfusion Essential Studio license validation?
- How to upgrade from Trial version after purchasing a license?
- Where can I get a license key?
diff --git a/wpf/Licensing/ci-license-validation.md b/wpf/Licensing/ci-license-validation.md
deleted file mode 100644
index 69c5ca560..000000000
--- a/wpf/Licensing/ci-license-validation.md
+++ /dev/null
@@ -1,110 +0,0 @@
----
-layout: post
-title: Overview of Syncfusion license validation in CI services - Syncfusion
-description: Learn here about how to register Syncfusion license key for Syncfusion application for license validation.
-platform: wpf
-control: Essential Studio
-documentation: ug
----
-
-
-
-
-# Syncfusion license key validation in CI services
-
-Syncfusion license key validation in CI services ensures that Syncfusion Essential Studio components are properly licensed during CI processes, Validating the license key at the CI level can prevent licensing errors during deployment. The following section shows how to validate the Syncfusion license key in CI services.
-
-* Download and extract the LicenseKeyValidator.zip utility from the following link: [LicenseKeyValidator](https://s3.amazonaws.com/files2.syncfusion.com/Installs/LicenseKeyValidation/LicenseKeyValidator.zip).
-
-* Open the LicenseKeyValidation.ps1 PowerShell script in a text\code editor.
-
-
-
-* Update the parameters in the LicenseKeyValidation.ps1 script file as described below.
-
- **Platform:** Modify the value for /platform: to the actual platform "WPF".
-
- **Version:** Change the value for /version: to the required version (e.g., "26.2.4").
-
- **License Key:** Replace the value for /licensekey: with your actual license key (e.g., "Your License Key").
-
- N> This feature is supported only from the 16.2.0.41 version of the Essential Studio.
-
-## Azure Pipelines (YAML)
-
-* Create a new [User-defined Variable](https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#user-defined-variables) named `LICENSE_VALIDATION` in Azure Pipeline. Use the path of the LicenseKeyValidation.ps1 script file as a value (e.g., D:\LicenseKeyValidator\LicenseKeyValidation.ps1).
-
-* Integrate the PowerShell task in pipeline and execute the script to validate the license key.
-
-The following example shows the syntax for Windows build agents.
-
-```bash
-pool:
- vmImage: 'windows-latest'
-
-steps:
-
-- task: PowerShell@2
- inputs:
- targetType: filePath
- filePath: $(LICENSE_VALIDATION) #Or the actual path to the script.
-
- displayName: Syncfusion License Validation
-```
-
-## Azure Pipelines (Classic)
-
-* Create a new [User-defined Variable](https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#user-defined-variables) named `LICENSE_VALIDATION` in Azure Pipeline. Use the path of the LicenseKeyValidation.ps1 script file as a value (e.g., D:\LicenseKeyValidator\LicenseKeyValidation.ps1).
-
-* Include the PowerShell task in pipeline and execute the script to validate the license key.
-
-
-
-## GitHub actions
-
-* To execute the script in PowerShell as part of a GitHub Actions workflow, include a step in the configuration file and update the path of the LicenseKeyValidation.ps1 script file (e.g., D:\LicenseKeyValidator\LicenseKeyValidation.ps1).
-
-The following example shows the syntax for validating Syncfusion license key in GitHub actions.
-
-```bash
- steps:
- - name: Syncfusion License Validation
- shell: pwsh
- run: |
- ./path/LicenseKeyValidator/LicenseKeyValidation.ps1
-```
-
-## Jenkins
-
-* Create a [Environment Variable](https://www.jenkins.io/doc/pipeline/tour/environment) named 'LICENSE_VALIDATION'. Use Use the path of the LicenseKeyValidation.ps1 script file as a value (e.g., D:\LicenseKeyValidator\LicenseKeyValidation.ps1).
-
-* Include a stage in Jenkins to execute the LicenseKeyValidation.ps1 script in PowerShell.
-
-The following example shows the syntax for validating Syncfusion license key in Jenkins pipeline.
-
-```bash
-pipeline {
- agent any
- environment {
- LICENSE_VALIDATION = 'path\\to\\LicenseKeyValidator\\LicenseKeyValidation.ps1'
- }
- stages {
- stage('Syncfusion License Validation') {
- steps {
- sh 'pwsh ${LICENSE_VALIDATION}'
- }
- }
- }
-}
-```
-
-## See also
-
-* [Licensing FAQ](https://help.syncfusion.com/common/essential-studio/licensing/overview/)
diff --git a/wpf/Licensing/licensing-images/license-validation-classic.png b/wpf/Licensing/licensing-images/license-validation-classic.png
deleted file mode 100644
index 1370fd173..000000000
Binary files a/wpf/Licensing/licensing-images/license-validation-classic.png and /dev/null differ
diff --git a/wpf/Licensing/licensing-images/license-validation.png b/wpf/Licensing/licensing-images/license-validation.png
deleted file mode 100644
index a4396f695..000000000
Binary files a/wpf/Licensing/licensing-images/license-validation.png and /dev/null differ