Microsoft.ResourceNotifications - Adding new resource type and APIs(ResourceSubscription, Destinations)

[Priyanarang]

• Add comprehensive TypeSpec-based API specification for Microsoft.ResourceNotifications
• Implement ResourceSubscription resource with tenant/cloud scope support
• Add Destination extension resource with fabric table and storage account types
• Support discriminated unions for polymorphic properties (scope, partitioning, destinations)
• Include ARN location partitioning configuration with partition definitions
• Add path policies for time and scope range hash-based routing
• Support batching policies with minimum count and maximum delay configuration
• Provide complete CRUD operations for both resources with ARM compliance
• Include comprehensive example files for all API operations
• Generate ARM-compliant OpenAPI specification with proper pagination support
• Support multi-language SDK generation (C#, Python, Java, JavaScript, Go)
• API version: 2025-11-11-preview

Choose a PR Template

Switch to "Preview" on this description then select one of the choices below.

Click here to open a PR for a Data Plane API.

Click here to open a PR for a Control Plane (ARM) API.

Click here to open a PR for only SDK configuration.

[github-actions]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
• ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
  This PR is not ready for ARM review (label: NotReadyForARMReview). This PR will not be reviewed by ARM until relevant problems are fixed. Consult the rest of this Next Steps to Merge comment for details.
  Once the blocking problems are addressed, add to the PR a comment with contents /azp run. Automation will re-evaluate this PR and if everything looks good, it will add WaitForARMFeedback label which will put this PR on the ARM review queue.
  For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  
• ❌ This PR is NotReadyForARMReview because it has the CI-NewRPNamespaceWithoutRPaaS label.
  
• ❌ This PR has CI-NewRPNamespaceWithoutRPaaS label. This means it is introducing a new RP (Resource Provider) namespace that has not been onboarded with RPaaS. Merging this PR to the main branch is blocked as RPaaS is required for new RPs.
  To resolve, use RPaaS to onboard the new RP. To apply for exception, see aka.ms/RPaaSException.

Comment generated by summarize-checks workflow run.

[github-actions]

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language	API Review for Package
TypeSpec	Microsoft.ResourceNotifications
Python	azure-mgmt-resourcenotifications
C#	Azure.ResourceManager.ResourceNotifications
JavaScript	@azure/arm-resourcenotifications
Java	com.azure.resourcemanager:azure-resourcemanager-resourcenotifications
Go	sdk/resourcemanager/resourcenotifications/armresourcenotifications