[TypeSpec] Create Liftr Elastic Azure Integration specification for SDK generation

[Copilot]

This PR creates a complete TypeSpec specification for the Liftr - Elastic Azure Integration SaaS offer on Marketplace to enable SDK generation across multiple languages (.NET, Java, JavaScript, Python, Go).

Overview

The Liftr - Elastic Azure Integration service provides monitoring and observability capabilities through Elastic's search and analytics platform, integrated seamlessly with Azure services. This implementation follows the established Liftr service patterns used by other marketplace integrations like MongoDB Atlas.

Changes Made

TypeSpec Specification

• Created complete TypeSpec specification at specification/liftrelastic/ElasticAzure.Management/
• Namespace: ElasticAzure with API version 2025-06-30-preview
• Resource Model: OrganizationResource following Azure Resource Manager patterns
• Operations: Full CRUD operations (GET, PUT, PATCH, DELETE, LIST)

Key Features

• Elastic Azure Properties: Configuration for organization ID, redirect URL, and organization name
• Marketplace Integration: Full Azure Marketplace billing and subscription management via LiftrBase
• ARM Compliance: Follows Azure Resource Manager conventions with proper lifecycle management

SDK Configuration

Configured SDK generation for all required languages:

• Go: armelasticazure
• Java: azure-resourcemanager-elasticazure
• JavaScript: @azure/arm-elasticazure
• Python: azure-mgmt-elasticazure
• .NET: Azure.ResourceManager.ElasticAzure

Files Created

• main.tsp - Core TypeSpec specification with resource definitions
• client.tsp - Client-specific customizations for all SDK languages
• tspconfig.yaml - SDK generation configuration
• cspell.yaml - Spell checking configuration
• Example structure for API usage demonstrations
• Generated OpenAPI specification

Validation

• ✅ TypeSpec compiles successfully without errors
• ✅ Passes all Azure Resource Manager validation rules
• ✅ Follows established Liftr service patterns
• ✅ Configured for beta release as specified in release plan

Release Plan Integration

Updated release plan work item 28204 with SDK package details for all languages. The specification is now ready for official SDK generation through Azure SDK pipelines.

Fixes #36295.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[openapi-pipeline-app]

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).
• ❌ The required check named Swagger ModelValidation has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide

[openapi-pipeline-app]

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.