Deprecate legacy Azure storage support

docs/src/main/sphinx/object-storage.md

@@ -78,7 +78,6 @@ object storage system as *legacy* support. Additional documentation is available
 with the Hive connector and relevant dedicated pages:
 
 - [](/connector/hive)
-- [](/object-storage/legacy-azure)
 - [](/object-storage/legacy-gcs)
 - [](/object-storage/legacy-cos)
 - [](/object-storage/legacy-s3)
@@ -102,7 +101,6 @@ storage:
 /object-storage/file-system-gcs
 /object-storage/file-system-s3
 /object-storage/file-system-hdfs
-/object-storage/legacy-azure
 /object-storage/legacy-cos
 /object-storage/legacy-gcs
 /object-storage/legacy-s3

docs/src/main/sphinx/redirects.txt

@@ -11,6 +11,7 @@ connector/localfile.md connector/removed.md
 connector/accumulo.md connector/removed.md
 connector/kinesis.md connector/removed.md
 security/apache-ranger-access-control.md security/ranger-access-control.md
+object-storage/legacy-azure.md object-storage/file-system-azure.md
 routines.md udf.md
 routines/function.md udf/function.md
 routines/introduction.md udf/introduction.md

docs/src/main/sphinx/release/release-458.md

@@ -19,8 +19,8 @@
   all catalogs. You must activate the desired [file system
   support](file-system-configuration) with
   `fs.native-azure.enabled`,`fs.native-gcs.enabled`, `fs.native-s3.enabled`, or
-  `fs.hadoop.enabled` in each catalog. Use the migration guides for [Azure
-  Storage](fs-legacy-azure-migration), [Google Cloud
+  `fs.hadoop.enabled` in each catalog. Use the migration guides for Azure
+  Storage, [Google Cloud
   Storage](fs-legacy-gcs-migration), and [S3](fs-legacy-s3-migration) to assist
   if you have not switched from legacy support. ({issue}`23343`)
 * Add JMX monitoring to the [](/object-storage/file-system-s3). ({issue}`23177`)
@@ -38,8 +38,7 @@
   all catalogs. You must activate the desired [file system
   support](file-system-configuration) with
   `fs.native-azure.enabled`,`fs.native-gcs.enabled`, `fs.native-s3.enabled`, or
-  `fs.hadoop.enabled` in each catalog. Use the migration guides for [Azure
-  Storage](fs-legacy-azure-migration), [Google Cloud
+  `fs.hadoop.enabled` in each catalog. Use the migration guides for [Google Cloud
   Storage](fs-legacy-gcs-migration), and [S3](fs-legacy-s3-migration) to assist
   if you have not switched from legacy support. ({issue}`23343`)
 * Add JMX monitoring to the native S3 file system support. ({issue}`23177`)
@@ -56,8 +55,7 @@
   all catalogs. You must activate the desired [file system
   support](file-system-configuration) with
   `fs.native-azure.enabled`,`fs.native-gcs.enabled`, `fs.native-s3.enabled`, or
-  `fs.hadoop.enabled` in each catalog. Use the migration guides for [Azure
-  Storage](fs-legacy-azure-migration), [Google Cloud
+  `fs.hadoop.enabled` in each catalog. Use the migration guides for [Google Cloud
   Storage](fs-legacy-gcs-migration), and [S3](fs-legacy-s3-migration) to assist
   if you have not switched from legacy support. ({issue}`23343`)
 * Add JMX monitoring to the native S3 file system support. ({issue}`23177`)
@@ -69,8 +67,7 @@
   all catalogs. You must activate the desired [file system
   support](file-system-configuration) with
   `fs.native-azure.enabled`,`fs.native-gcs.enabled`, `fs.native-s3.enabled`, or
-  `fs.hadoop.enabled` in each catalog. Use the migration guides for [Azure
-  Storage](fs-legacy-azure-migration), [Google Cloud
+  `fs.hadoop.enabled` in each catalog. Use the migration guides for [Google Cloud
   Storage](fs-legacy-gcs-migration), and [S3](fs-legacy-s3-migration) to assist
   if you have not switched from legacy support. ({issue}`23343`)
 * Add JMX monitoring to the native S3 file system support. ({issue}`23177`)