Added link for custom parsing

Added a link to custom file extensions and custom parsers as it is not clear how the support for this works within the doc. Needs validation if the link is correct
-------
cc: @linda33wj

Author: svchandramohan

articles/purview/microsoft-purview-connector-overview.md

@@ -114,7 +114,7 @@ The following file types are supported for scanning, for schema extraction, and
  > * For delimited file types (CSV, PSV, SSV, TSV, TXT), we do not support data type detection. The data type will be listed as "string" for all columns. We only support comma(‘,’), semicolon(‘;’), vertical bar(‘|’) and tab(‘\t’) as delimiter. If the field doesn't have quotes on the ends, or the field is a single quote char or there are quotes within the field, the row will be judged as error row. Rows that have different number of columns than the header row will be judged as error rows. (numbers of error rows / numbers of rows sampled ) must be less than 0.1.
  > * For Parquet files, if you are using a self-hosted integration runtime, you need to install the **64-bit JRE 8 (Java Runtime Environment) or OpenJDK** on your IR machine. Check our [Java Runtime Environment section at the bottom of the page](manage-integration-runtimes.md#java-runtime-environment-installation) for an installation guide.
 - Document file formats supported by extension: DOC, DOCM, DOCX, DOT, ODP, ODS, ODT, PDF, POT, PPS, PPSX, PPT, PPTM, PPTX, XLC, XLS, XLSB, XLSM, XLSX, XLT
-- The Microsoft Purview Data Map also supports custom file extensions and custom parsers.
+- The Microsoft Purview Data Map also supports [custom file extensions and custom parsers](https://learn.microsoft.com/en-us/azure/purview/create-a-scan-rule-set#create-a-custom-file-type).
 
 ## Schema extraction