This is the Azure SDK parent repository and mostly contains documentation around guidelines and policies as well as the releases for the various languages supported by the Azure SDK.
Thank you for starting the process for approval of the client library for your Azure service. Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.
The Architecture Board reviews Track 2 libraries only. If your library does not meet this requirement, please reach out to Architecture Board before creating the issue.
Please reference our review process guidelines to understand what is being asked for in the issue template.
Before submitting, ensure you adjust the title of the issue appropriately.
Note that the required material must be included before a meeting can be scheduled.
Contacts and Timeline
Main contacts:
Strong Liu (@stliu, Spring Cloud Azure team lead)
Sean Li (@seanli1988, Spring Cloud Azure PM)
Xiaolu Dai (@saragluna)
Expected GA date for this library:
mid-March, 2022
About the Service
Spring is the most popular application development framework for enterprise Java. There are many Spring projects in the Spring ecosystem to take care of the different needs in application development. The Spring Cloud Azure team is working on the integration between Azure and Spring. We provide Azure support for different Spring projects, such as Spring Boot, Spring Data, Spring Integration, Spring Security, and Spring Cloud Stream.
Link to documentation introducing/describing the service:
Is the goal to release a Public Preview, Private Preview, or GA?
The Spring Cloud Azure libraries exist for years, and this time we are going to GA a major version, the Spring Cloud Azure 4.0, which is a refactored new version.
About the client library
Name of client library:
Spring Cloud Azure is our project name. And we will ship ~40 artifacts this time:
Is there an existing SDK library? If yes, provide link:
Yes, we have shipped these libraries before, but the artifact names are changed in this version.
https://repo1.maven.org/maven2/com/azure/spring/
Step 1: Champion Scenarios
Ultimately the library should be easy to use for common scenarios that developers want. Consider the following questions when thinking about champion scenarios:
What is the app the developer is building that uses your client library?
Typically a Spring or Spring Boot application.
Who is the end-user of the application (the developer's customer)?
The developer's customer.
What features of the API need to be explained in the sample so that someone could use this API in real app?
Will explain in the champion scenarios.
How does the authentication workflow look?
Build on top of azure sdks and azure-identity.
lilyjma
commented
2 years ago 
tg-msft
Thank you for starting the process for approval of the client library for your Azure service. Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.
The Architecture Board reviews Track 2 libraries only. If your library does not meet this requirement, please reach out to Architecture Board before creating the issue.
Please reference our review process guidelines to understand what is being asked for in the issue template.
Before submitting, ensure you adjust the title of the issue appropriately.
Note that the required material must be included before a meeting can be scheduled.
Contacts and Timeline
About the Service
Spring is the most popular application development framework for enterprise Java. There are many Spring projects in the Spring ecosystem to take care of the different needs in application development. The Spring Cloud Azure team is working on the integration between Azure and Spring. We provide Azure support for different Spring projects, such as Spring Boot, Spring Data, Spring Integration, Spring Security, and Spring Cloud Stream.
About the client library
Step 1: Champion Scenarios
Ultimately the library should be easy to use for common scenarios that developers want. Consider the following questions when thinking about champion scenarios:
See Champion Scenario section here.
Code is appreciated but optional. Pseudocode is fine.
Step 2: Quickstart Samples (Optional)
Include samples demonstrating how to consume the client library if available:
We have a sample repo hosting all our sample projects: https://github.com/Azure-Samples/azure-spring-boot-samples/tree/spring-cloud-azure_4.0.0-beta.3
Thank you for your submission!