Docs: Document unavailability of subscriptions in remote schemas

PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7475
GitOrigin-RevId: 60e5c30bac6f6f5633780ab56d1b535c95e7faa6

docs/docs/remote-schemas/index.mdx

@@ -42,13 +42,6 @@ You can handle these use cases by writing resolvers in a custom GraphQL server a
 schema" with the existing auto-generated schema. You can also add multiple Remote Schemas. Think of the merged schema as
 a union of top-level nodes from each of the sub-schemas.
 
-:::info Note
-
-If you are looking for adding authorization & access control for your app users to the GraphQL APIs that are
-auto-generated via Hasura, head to [Authentication & Authorization](/auth/index.mdx).
-
-:::
-
 :::info Health monitoring of Remote Schemas in Hasura Cloud
 
 Hasura Cloud offers built-in API metrics with integrated Health Checks and distributed tracing for your Remote Schemas.
@@ -56,6 +49,12 @@ Read more at [Distributed Tracing in Hasura Cloud](/observability/tracing.mdx).
 
 :::
 
+:::info Remote Schema Subscriptions
+
+Note that subscriptions are currently not supported for Remote Schemas.
+
+:::
+
 ## Learn more
 
 - [Adding a Remote Schema](/remote-schemas/adding-schema.mdx)

docs/docs/subscriptions/index.mdx

@@ -20,17 +20,15 @@ changes upstream.
 Subscriptions are supported for all kinds of queries. All the concepts of [queries](/queries/index.mdx) hold true for
 subscriptions as well.
 
-:::info Caveat
+:::info One root field in a subscription
 
 Hasura follows the [GraphQL spec](https://graphql.github.io/graphql-spec/June2018/#sec-Single-root-field) which allows
 for only one root field in a subscription.
 
 :::
 
-## Authentication
+Subscriptions are not currently supported for [remote schemas](/remote-schemas/index.mdx).
 
-For information about authenticating your subscriptions see the [authentication section](/auth/authentication/index.mdx)
-here.
 
 ## Explore subscriptions