Mock sample for your project: FeatureClient API

The Azure SQL Database management API provides a RESTful set of web APIs that interact with Azure SQL Database services to manage your databases. The API enables users to create, retrieve, update, and delete databases, servers, and other entities.

The User Subscription Management Client.

Azure Blueprints Client provides access to blueprint definitions, assignments, and artifacts, and related blueprint operations.

Storage system operation endpoints and objects.

The Disk Resource Provider Client.

The Update Admin Management Client.

The Run Commands Client.

These APIs allow end users to operate on Azure Machine Learning Web Services resources. They support the following operations: Create or update a web service Get a web service Patch a web service Delete a web service Get All Web Services in a Resource Group Get All Web Services in a Subscription Get Web Services Keys

Operation status operation endpoints and objects.

Azure Event Hubs client for managing Event Hubs Cluster, IPFilter Rules and VirtualNetworkRules resources.

The Admin Gallery Management Client.

Azure Application Insights client for API keys of a component.

AWS CloudHSM Service This is documentation for AWS CloudHSM Classic. For more information, see AWS CloudHSM Classic FAQs, the AWS CloudHSM Classic User Guide, and the AWS CloudHSM Classic API Reference. For information about the current version of AWS CloudHSM, see AWS CloudHSM, the AWS CloudHSM User Guide, and the AWS CloudHSM API Reference.

The Amazon SageMaker runtime API.

API spec for Microsoft.Security (Azure Security Center) resource provider

These APIs allow end users to manage Azure Machine Learning Models, Images, Profiles, and Services.

Use these REST APIs for performing operations on Tag entity in your Azure API Management deployment. Tags can be assigned to APIs, Operations and Products.

Microsoft Azure Mobile Engagement REST APIs.

Identity and Access Management Access Analyzer helps identify potential resource-access risks by enabling you to identify any policies that grant access to an external principal. It does this by using logic-based reasoning to analyze resource-based policies in your Amazon Web Services environment. An external principal can be another Amazon Web Services account, a root user, an IAM user or role, a federated user, an Amazon Web Services service, or an anonymous user. You can also use IAM Access Analyzer to preview and validate public and cross-account access to your resources before deploying permissions changes. This guide describes the Identity and Access Management Access Analyzer operations that you can call programmatically. For general information about IAM Access Analyzer, see Identity and Access Management Access Analyzer in the IAM User Guide. To start using IAM Access Analyzer, you first need to create an analyzer.

Azure Application Insights client for favorites.