Microsoft Azure Support provides technical assistance and guidance to customers using the Azure cloud computing platform. The support team is available 24/7 to help with troubleshooting issues, answering questions, and addressing any concerns that users may have. They offer various levels of support, ranging from basic to premium, to cater to the specific needs and requirements of individual customers.
swagger: '2.0'
info:
version: 2022-09-01-preview
title: Microsoft Azure Microsoft.Support
description: Microsoft Azure Support Resource Provider.
host: management.azure.com
schemes:
- https
consumes:
- application/json
produces:
- application/json
security:
- azure_auth:
- user_impersonation
securityDefinitions:
azure_auth:
flow: implicit
authorizationUrl: https://login.microsoftonline.com/common/oauth2/authorize
scopes:
user_impersonation: impersonate your user account
type: oauth2
description: Azure Active Directory OAuth2 Flow.
paths:
/providers/Microsoft.Support/operations:
get:
tags:
- Operations
description: This lists all the available Microsoft Support REST API operations.
operationId: microsoftAzureOperationsList
parameters:
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: Successfully retrieved list of operations.
schema:
$ref: '#/definitions/OperationsListResult'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-pageable:
nextLinkName:
x-ms-examples:
Get all operations:
$ref: ./examples/ListOperations.json
summary: Microsoft Azure Get Providers Microsoft Support Operations
/providers/Microsoft.Support/services:
get:
tags: []
description: >-
Lists all the Azure services available for support ticket creation. For
**Technical** issues, select the Service Id that maps to the Azure
service/product as displayed in the **Services** drop-down list on the
Azure portal's [New support
request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview)
page. Always use the service and its corresponding problem
classification(s) obtained programmatically for support ticket creation.
This practice ensures that you always have the most recent set of
service and problem classification Ids.
operationId: microsoftAzureServicesList
parameters:
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: >-
Successfully retrieved list of the Azure services available for
support.
schema:
$ref: '#/definitions/ServicesListResult'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-pageable:
nextLinkName:
x-ms-examples:
Gets list of services for which a support ticket can be created:
$ref: ./examples/ListServices.json
summary: Microsoft Azure Get Providers Microsoft Support Services
/providers/Microsoft.Support/services/{serviceName}:
get:
tags: []
description: Gets a specific Azure service for support ticket creation.
operationId: microsoftAzureServicesGet
parameters:
- name: serviceName
in: path
description: Name of the Azure service.
required: true
type: string
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: Successfully retrieved Azure service for support ticket creation.
schema:
$ref: '#/definitions/Service'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-examples:
Gets details of the Azure service:
$ref: ./examples/GetService.json
summary: Microsoft Azure Get Providers Microsoft Support Services Servicename
/providers/Microsoft.Support/services/{serviceName}/problemClassifications:
get:
tags:
- ProblemClassifications
description: >-
Lists all the problem classifications (categories) available for a
specific Azure service. Always use the service and problem
classifications obtained programmatically. This practice ensures that
you always have the most recent set of service and problem
classification Ids.
operationId: microsoftAzureProblemclassificationsList
parameters:
- name: serviceName
in: path
description: >-
Name of the Azure service for which the problem classifications need
to be retrieved.
required: true
type: string
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: >-
Successfully retrieved list of problem classifications for the
specified Azure service.
schema:
$ref: '#/definitions/ProblemClassificationsListResult'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-pageable:
nextLinkName:
x-ms-examples:
Gets list of problemClassifications for a service for which a support ticket can be created:
$ref: ./examples/ListProblemClassifications.json
summary: >-
Microsoft Azure Get Providers Microsoft Support Services Servicename Problemclassifications
/providers/Microsoft.Support/services/{serviceName}/problemClassifications/{problemClassificationName}:
get:
tags:
- ProblemClassifications
description: Get problem classification details for a specific Azure service.
operationId: microsoftAzureProblemclassificationsGet
parameters:
- name: serviceName
in: path
description: Name of the Azure service available for support.
required: true
type: string
- name: problemClassificationName
in: path
description: Name of problem classification.
required: true
type: string
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: Successfully retrieved problem classification details.
schema:
$ref: '#/definitions/ProblemClassification'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-examples:
Gets details of problemClassification for Azure service:
$ref: ./examples/GetProblemClassification.json
summary: >-
Microsoft Azure Get Providers Microsoft Support Services Servicename Problemclassifications Problemclassificationname
/subscriptions/{subscriptionId}/providers/Microsoft.Support/checkNameAvailability:
post:
tags:
- SupportTickets
description: >-
Check the availability of a resource name. This API should be used to
check the uniqueness of the name for support ticket creation for the
selected subscription.
operationId: microsoftAzureSupportticketsChecknameavailability
x-ms-examples:
Checks whether name is available for SupportTicket resource:
$ref: ./examples/CheckNameAvailabilityWithSubscription.json
parameters:
- name: checkNameAvailabilityInput
in: body
description: Input to check.
required: true
schema:
$ref: '#/definitions/CheckNameAvailabilityInput'
- $ref: '#/parameters/SubscriptionIdParameter'
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: OK. The request has succeeded.
schema:
$ref: '#/definitions/CheckNameAvailabilityOutput'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
summary: >-
Microsoft Azure Post Subscriptions Subscriptionid Providers Microsoft Support Checknameavailability
/providers/Microsoft.Support/checkNameAvailability:
post:
tags:
- SupportTickets
description: >-
Check the availability of a resource name. This API should be used to
check the uniqueness of the name for support ticket creation for the
selected subscription.
operationId: microsoftAzureSupportticketsnosubscriptionChecknameavailability
x-ms-examples:
Checks whether name is available for SupportTicket resource:
$ref: ./examples/CheckNameAvailability.json
parameters:
- name: checkNameAvailabilityInput
in: body
description: Input to check.
required: true
schema:
$ref: '#/definitions/CheckNameAvailabilityInput'
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: OK. The request has succeeded.
schema:
$ref: '#/definitions/CheckNameAvailabilityOutput'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
summary: Microsoft Azure Post Providers Microsoft Support Checknameavailability
/subscriptions/{subscriptionId}/providers/Microsoft.Support/supportTickets:
get:
tags:
- SupportTickets
description: >-
Lists all the support tickets for an Azure subscription. You can also
filter the support tickets by _Status_, _CreatedDate_, _ServiceId_, and
_ProblemClassificationId_ using the $filter parameter. Output will be a
paged result with _nextLink_, using which you can retrieve the next set
of support tickets. Support ticket data is available for 18 months after
ticket creation. If a ticket was created more than 18 months ago, a
request for data might cause an error.
operationId: microsoftAzureSupportticketsList
parameters:
- name: $top
in: query
description: >-
The number of values to return in the collection. Default is 25 and
max is 100.
required: false
type: integer
format: int32
- name: $filter
in: query
required: false
type: string
description: >-
The filter to apply on the operation. We support 'odata v4.0' filter
semantics. [Learn
more](https://docs.microsoft.com/odata/concepts/queryoptions-overview).
_Status_, _ServiceId_, and _ProblemClassificationId_ filters can
only be used with Equals ('eq') operator. For _CreatedDate_ filter,
the supported operators are Greater Than ('gt') and Greater Than or
Equals ('ge'). When using both filters, combine them using the
logical 'AND'.
- $ref: '#/parameters/SubscriptionIdParameter'
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: Successfully retrieved support tickets.
schema:
$ref: '#/definitions/SupportTicketsListResult'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-pageable:
nextLinkName: nextLink
x-ms-examples:
List support tickets for a subscription:
$ref: ./examples/ListSupportTicketsBySubscription.json
List support tickets in open state for a subscription:
$ref: ./examples/ListSupportTicketsInOpenStateBySubscription.json
List support tickets created on or after a certain date and in open state for a subscription:
$ref: >-
./examples/ListSupportTicketsCreatedOnOrAfterAndInOpenStateBySubscription.json
List support tickets in updating state for a subscription:
$ref: ./examples/ListSupportTicketsInUpdatingStateBySubscription.json
List support tickets created on or after a certain date and in updating state for a subscription:
$ref: >-
./examples/ListSupportTicketsCreatedOnOrAfterAndInUpdatingStateBySubscription.json
List support tickets with a certain service id for a subscription:
$ref: ./examples/ListSupportTicketsServiceIdEqualsForSubscription.json
List support tickets with a certain problem classification id for a subscription:
$ref: >-
./examples/ListSupportTicketsProblemClassificationIdEqualsForSubscription.json
summary: >-
Microsoft Azure Get Subscriptions Subscriptionid Providers Microsoft Support Supporttickets
/providers/Microsoft.Support/supportTickets:
get:
tags:
- SupportTickets
description: >-
Lists all the support tickets. You can also filter the support tickets
by Status, CreatedDate, , ServiceId, and ProblemClassificationId using
the $filter parameter. Output will be a paged result with nextLink,
using which you can retrieve the next set of support tickets. Support
ticket data is available for 18 months after ticket creation. If a
ticket was created more than 18 months ago, a request for data might
cause an error.
operationId: microsoftAzureSupportticketsnosubscriptionList
parameters:
- name: $top
in: query
description: >-
The number of values to return in the collection. Default is 25 and
max is 100.
required: false
type: integer
format: int32
- name: $filter
in: query
required: false
type: string
description: >-
The filter to apply on the operation. We support 'odata v4.0' filter
semantics. <a target='_blank'
href='https://docs.microsoft.com/odata/concepts/queryoptions-overview'>Learn
more</a> <br/><i>Status</i> , <i>ServiceId</i>, and
<i>ProblemClassificationId</i> filters can only be used with 'eq'
operator. For <i>CreatedDate</i> filter, the supported operators are
'gt' and 'ge'. When using both filters, combine them using the
logical 'AND'.
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: Successfully retrieved support tickets.
schema:
$ref: '#/definitions/SupportTicketsListResult'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-pageable:
nextLinkName: nextLink
x-ms-examples:
List support tickets for a subscription:
$ref: ./examples/ListSupportTickets.json
List support tickets in open state for a subscription:
$ref: ./examples/ListSupportTicketsInOpenState.json
List support tickets created on or after a certain date and in open state for a subscription:
$ref: ./examples/ListSupportTicketsCreatedOnOrAfterAndInOpenState.json
List support tickets in updating state for a subscription:
$ref: ./examples/ListSupportTicketsInUpdatingState.json
List support tickets created on or after a certain date and in updating state for a subscription:
$ref: ./examples/ListSupportTicketsCreatedOnOrAfterAndInUpdatingState.json
List support tickets with a certain service id for a subscription:
$ref: ./examples/ListSupportTicketsServiceIdEquals.json
List support tickets with a certain problem classification id for a subscription:
$ref: ./examples/ListSupportTicketsProblemClassificationIdEquals.json
summary: Microsoft Azure Get Providers Microsoft Support Supporttickets
/subscriptions/{subscriptionId}/providers/Microsoft.Support/supportTickets/{supportTicketName}:
get:
tags:
- SupportTickets
description: >-
Get ticket details for an Azure subscription. Support ticket data is
available for 18 months after ticket creation. If a ticket was created
more than 18 months ago, a request for data might cause an error.
operationId: microsoftAzureSupportticketsGet
parameters:
- name: supportTicketName
in: path
description: Support ticket name.
required: true
type: string
- $ref: '#/parameters/SubscriptionIdParameter'
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: Successfully retrieved support ticket.
schema:
$ref: '#/definitions/SupportTicketDetails'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-examples:
Get details of a subscription ticket:
$ref: ./examples/GetSubscriptionSupportTicketDetails.json
summary: >-
Microsoft Azure Get Subscriptions Subscriptionid Providers Microsoft Support Supporttickets Supportticketname
patch:
tags:
- SupportTickets
description: >-
This API allows you to update the severity level, ticket status,
advanced diagnostic consent and your contact information in the support
ticket.Note: The severity levels cannot be changed if a support ticket
is actively being worked upon by an Azure support engineer. In such a
case, contact your support engineer to request severity update by adding
a new communication using the Communications API.
operationId: microsoftAzureSupportticketsUpdate
parameters:
- name: supportTicketName
in: path
description: Support ticket name.
required: true
type: string
- name: updateSupportTicket
in: body
description: UpdateSupportTicket object.
required: true
schema:
$ref: '#/definitions/UpdateSupportTicket'
- $ref: '#/parameters/SubscriptionIdParameter'
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: Successfully updated support ticket.
schema:
$ref: '#/definitions/SupportTicketDetails'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-examples:
Update severity of a support ticket:
$ref: ./examples/UpdateSeverityOfSupportTicketForSubscription.json
Update contact details of a support ticket:
$ref: ./examples/UpdateContactDetailsOfSupportTicketForSubscription.json
Update status of a support ticket:
$ref: ./examples/UpdateStatusOfSupportTicketForSubscription.json
Update advanced diagnostic consent of a support ticket:
$ref: >-
./examples/UpdateAdvancedDiagnosticConsentOfSupportTicketForSubscription.json
summary: >-
Microsoft Azure Patch Subscriptions Subscriptionid Providers Microsoft Support Supporttickets Supportticketname
put:
tags:
- SupportTickets
description: >-
Creates a new support ticket for Subscription and Service limits
(Quota), Technical, Billing, and Subscription Management issues for the
specified subscription. Learn the
[prerequisites](https://aka.ms/supportAPI) required to create a support
ticket.Always call the Services and ProblemClassifications API to get
the most recent set of services and problem categories required for
support ticket creation.Adding attachments is not currently supported
via the API. To add a file to an existing support ticket, visit the
[Manage support
ticket](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/managesupportrequest)
page in the Azure portal, select the support ticket, and use the file
upload control to add a new file.Providing consent to share diagnostic
information with Azure support is currently not supported via the API.
The Azure support engineer working on your ticket will reach out to you
for consent if your issue requires gathering diagnostic information from
your Azure resources.**Creating a support ticket for on-behalf-of**:
Include _x-ms-authorization-auxiliary_ header to provide an auxiliary
token as per
[documentation](https://docs.microsoft.com/azure/azure-resource-manager/management/authenticate-multi-tenant).
The primary token will be from the tenant for whom a support ticket is
being raised against the subscription, i.e. Cloud solution provider
(CSP) customer tenant. The auxiliary token will be from the Cloud
solution provider (CSP) partner tenant.
operationId: microsoftAzureSupportticketsCreate
parameters:
- name: supportTicketName
in: path
description: Support ticket name.
required: true
type: string
- name: createSupportTicketParameters
in: body
description: Support ticket request payload.
required: true
schema:
$ref: '#/definitions/SupportTicketDetails'
- $ref: '#/parameters/SubscriptionIdParameter'
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: OK - SupportTicket created successfully.
schema:
$ref: '#/definitions/SupportTicketDetails'
'202':
description: Accepted, SupportTicket will be created asynchronously.
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-long-running-operation: true
x-ms-long-running-operation-options:
final-state-via: azure-async-operation
x-ms-examples:
Create a ticket for Billing related issues:
$ref: ./examples/CreateBillingSupportTicketForSubscription.json
Create a ticket for Subscription Management related issues:
$ref: ./examples/CreateSubMgmtSupportTicketForSubscription.json
Create a ticket for Technical issue related to a specific resource:
$ref: ./examples/CreateTechnicalSupportTicketForSubscription.json
Create a ticket to request Quota increase for Compute VM Cores:
$ref: ./examples/CreateCoresQuotaTicketForSubscription.json
Create a ticket to request Quota increase for Low-priority cores for a Batch account:
$ref: >-
./examples/CreateBatchQuotaTicketForSpecificBatchAccountForLowPriorityCores.json
Create a ticket to request Quota increase for specific VM family cores for a Batch account:
$ref: >-
./examples/CreateBatchQuotaTicketForSpecificBatchAccountForDedicatedCores.json
Create a ticket to request Quota increase for Pools for a Batch account:
$ref: >-
./examples/CreateBatchQuotaTicketForSpecificBatchAccountForPools.json
Create a ticket to request Quota increase for Active Jobs and Job Schedules for a Batch account:
$ref: >-
./examples/CreateBatchQuotaTicketForSpecificBatchAccountForActiveJobs.json
Create a ticket to request Quota increase for Batch accounts for a subscription:
$ref: ./examples/CreateBatchQuotaTicketForSubscription.json
Create a ticket to request Quota increase for DTUs for SQL Database:
$ref: ./examples/CreateSqlDatabaseQuotaTicketForDTUs.json
Create a ticket to request Quota increase for Servers for SQL Database:
$ref: ./examples/CreateSqlDatabaseQuotaTicketForServers.json
Create a ticket to request Quota increase for DTUs for Azure Synapse Analytics:
$ref: ./examples/CreateSqlDatawarehouseQuotaTicketForDTUs.json
Create a ticket to request Quota increase for Servers for Azure Synapse Analytics:
$ref: ./examples/CreateSqlDatawarehouseQuotaTicketForServers.json
Create a ticket to request Quota increase for specific VM family cores for Machine Learning service:
$ref: ./examples/CreateMachineLearningQuotaTicketForDedicatedCores.json
Create a ticket to request Quota increase for Low-priority cores for Machine Learning service:
$ref: ./examples/CreateMachineLearningQuotaTicketForLowPriorityCores.json
Create a ticket to request Quota increase for Azure SQL managed instance:
$ref: ./examples/CreateSqlManagedInstanceQuotaTicket.json
? Create a ticket to request Quota increase for services that do not require additional details in the quotaTicketDetails object
: $ref: ./examples/CreateGenericQuotaTicket.json
summary: >-
Microsoft Azure Put Subscriptions Subscriptionid Providers Microsoft Support Supporttickets Supportticketname
/providers/Microsoft.Support/supportTickets/{supportTicketName}:
get:
tags:
- SupportTickets
description: >-
Gets details for a specific support ticket. Support ticket data is
available for 18 months after ticket creation. If a ticket was created
more than 18 months ago, a request for data might cause an error.
operationId: microsoftAzureSupportticketsnosubscriptionGet
parameters:
- name: supportTicketName
in: path
description: Support ticket name.
required: true
type: string
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: Successfully retrieved support ticket.
schema:
$ref: '#/definitions/SupportTicketDetails'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-examples:
Get details of a ticket:
$ref: ./examples/GetSupportTicketDetails.json
summary: Microsoft Azure Get Providers Microsoft Support Supporttickets Supportticketname
patch:
tags:
- SupportTickets
description: >-
This API allows you to update the severity level, ticket status, and
your contact information in the support ticket.Note: The severity levels
cannot be changed if a support ticket is actively being worked upon by
an Azure support engineer. In such a case, contact your support engineer
to request severity update by adding a new communication using the
Communications API.
operationId: microsoftAzureSupportticketsnosubscriptionUpdate
parameters:
- name: supportTicketName
in: path
description: Support ticket name.
required: true
type: string
- name: updateSupportTicket
in: body
description: UpdateSupportTicket object.
required: true
schema:
$ref: '#/definitions/UpdateSupportTicket'
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: Successfully updated support ticket.
schema:
$ref: '#/definitions/SupportTicketDetails'
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-examples:
Update severity of a support ticket:
$ref: ./examples/UpdateSeverityOfSupportTicket.json
Update contact details of a support ticket:
$ref: ./examples/UpdateContactDetailsOfSupportTicket.json
Update status of a support ticket:
$ref: ./examples/UpdateStatusOfSupportTicket.json
Update advanced diagnostic consent of a support ticket:
$ref: ./examples/UpdateAdvancedDiagnosticConsentOfSupportTicket.json
summary: Microsoft Azure Patch Providers Microsoft Support Supporttickets Supportticketname
put:
tags:
- SupportTickets
description: >-
Creates a new support ticket for Billing, and Subscription Management
issues. Learn the [prerequisites](https://aka.ms/supportAPI) required to
create a support ticket.Always call the Services and
ProblemClassifications API to get the most recent set of services and
problem categories required for support ticket creation.Adding
attachments is not currently supported via the API. To add a file to an
existing support ticket, visit the [Manage support
ticket](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/managesupportrequest)
page in the Azure portal, select the support ticket, and use the file
upload control to add a new file.Providing consent to share diagnostic
information with Azure support is currently not supported via the API.
The Azure support engineer working on your ticket will reach out to you
for consent if your issue requires gathering diagnostic information from
your Azure resources.
operationId: microsoftAzureSupportticketsnosubscriptionCreate
parameters:
- name: supportTicketName
in: path
description: Support ticket name.
required: true
type: string
- name: createSupportTicketParameters
in: body
description: Support ticket request payload.
required: true
schema:
$ref: '#/definitions/SupportTicketDetails'
- $ref: '#/parameters/ApiVersionParameter'
responses:
'200':
description: OK - SupportTicket created successfully.
schema:
$ref: '#/definitions/SupportTicketDetails'
'202':
description: Accepted, SupportTicket will be created asynchronously.
headers:
Location:
type: string
default:
description: Error response describing why the operation failed.
schema:
$ref: >-
../../../../../common-types/resource-management/v5/types.json#/definitions/ErrorResponse
x-ms-long-running-operation: true
x-ms-long-running-operation-options:
final-state-via: azure-async-operation
x-ms-examples:
Create a ticket for Billing related issues:
$ref: ./examples/CreateBillingSupportTicket.json
Create a ticket for Subscription Management related issues:
$ref: ./examples/CreateSubMgmtSupportTicket.json
Create a ticket for Technical issue related to a specific resource:
$ref: ./examples/CreateTechnicalSupportTicket.json
summary: Microsoft Azure Put Providers Microsoft Support Supporttickets Supportticketname
/subscriptions/{subscriptionId}/providers/Microsoft.Support/supportTickets/{supportTicketName}/checkNameAvailability:
post:
tags:
- Communications
description: >-
Check the availability of a resource name. This API should be used to
check the uniqueness of the name for adding a new communication to the
support ticket.
operationId: microsoftAzureCommunicationsChecknameavailability
x-ms-examples:
Checks whether name is available for Communication resource:
$ref: ./examples/CheckNameAvailabilityForSupportTicketCommunication.json
# --- truncated at 32 KB (93 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/microsoft-azure/refs/heads/main/openapi/microsoftsupport-openapi-original.yml