Proposed guidance on Adopting Preview Items on Azure #289
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elerivaliant
reviewed
Jun 5, 2025
|
|
||
| ## Monitoring | ||
|
|
||
| It is not possible to centrally monitor enabled preview features. Therefore the responsibility for removing the feature should lie with the developer/staff member who enabled it. No newline at end of file |
There was a problem hiding this comment.
Suggested change
| It is not possible to centrally monitor enabled preview features. Therefore the responsibility for removing the feature should lie with the developer/staff member who enabled it. | |
| It is not possible to centrally monitor enabled preview features. Therefore the responsibility for removing the feature should lie with the engineering team or individual who requested it. |
elerivaliant
reviewed
Jun 5, 2025
| @@ -0,0 +1,39 @@ | |||
| ## DRAFT Preview Items policy | |||
There was a problem hiding this comment.
Suggested change
| ## DRAFT Preview Items policy | |
| ## Azure Preview Items Policy |
elerivaliant
reviewed
Jun 5, 2025
| To give some guidance on considerations when a preview item is required on an Azure subscription. | ||
|
|
||
| ## Before enabling a preview feaure | ||
| Decide upon the reason for enabling the feature: There is a caveat with preview features - they may never go into GA , may be in preview for many months (or even years) and may be withdrawn. |
There was a problem hiding this comment.
Suggested change
| Decide upon the reason for enabling the feature: There is a caveat with preview features - they may never go into GA , may be in preview for many months (or even years) and may be withdrawn. | |
| Decide upon the reason for enabling the feature. **Be aware of the caveats with preview features** - they may never go into GA, may be in preview for many months (or even years) and may be withdrawn. |
elerivaliant
reviewed
Jun 5, 2025
|
|
||
| Some features must be enabled by contacting Microsoft. | ||
|
|
||
| The feature should be enabled on Dev or Test subscription to begin with and then the functionality tested |
There was a problem hiding this comment.
Suggested change
| The feature should be enabled on Dev or Test subscription to begin with and then the functionality tested | |
| The feature should be enabled on Dev or Test subscriptions to begin with to test the functionality. |
elerivaliant
reviewed
Jun 5, 2025
|
|
||
| The feature should be enabled on Dev or Test subscription to begin with and then the functionality tested | ||
|
|
||
| If any adverse affects are seen , it should be removed (unregistered). |
There was a problem hiding this comment.
Suggested change
| If any adverse affects are seen , it should be removed (unregistered). | |
| If any adverse affects are seen, it should be removed (unregistered). |
elerivaliant
reviewed
Jun 5, 2025
|
|
||
| A provisioned service which depends on a preview feature could cease to function after a period of time. | ||
|
|
||
| It is highly recommended not to adopt any Azure preview feature in any production or live environment until it has been designated as GA by Microsoft. If there is a business need to do it, it should be approved by senior management (tbc). |
There was a problem hiding this comment.
Suggested change
| It is highly recommended not to adopt any Azure preview feature in any production or live environment until it has been designated as GA by Microsoft. If there is a business need to do it, it should be approved by senior management (tbc). | |
| It is highly recommended **not** to adopt any Azure preview feature in any production or live environment until it has been designated as GA by Microsoft. If there is a genuine business need, it should be approved by senior management and added to a risk register with appropriate consideration for the business criticality of the system using it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DDC have suggested that a preview policy be written when Azure preview features are required on a Subscription. This is a draft policy for anyone to comment.