Docs.MS Release Updates for azure-sdk-template

[azure-sdk]

Update docs metadata and targeting for release of azure-sdk-template

[opbld32]

Docs Build status updates of commit 2aa8616:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs-ref-services/preview/sdk-template-readme.md	⚠️Warning	View (azure-java-preview || azure-java-stable || azure-java-legacy)	Details

docs-ref-services/preview/sdk-template-readme.md

• Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
• Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
• Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'templatetemplate'.
• Line 56, Column 78: [Warning-bookmark-not-found] Cannot find bookmark '#introduction' in 'docs-ref-services/preview/sdk-template-readme.md'.
• Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
• Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Azure Batch client library for Python' is duplicated in: 'docs-ref-services/preview/sdk-template-readme.md(2,8), docs-ref-services/sdk-template-readme.md(2,8), docs-ref-services/sdk-template-readme-pre.md(2,8)'. Titles must be unique within a docset.
• Line 14, Column 1: [Suggestion-duplicate-h1s] H1 'README.md template' is duplicated with other articles: 'docs-ref-services/preview/sdk-template-readme.md(14,1), docs-ref-services/sdk-template-readme.md(14,1), docs-ref-services/sdk-template-readme-pre.md(14,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel