Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Who to contact for certified connector deployment issues and is there a revert process? #3757

Open
ahlivehr opened this issue Jan 15, 2025 · 0 comments

Comments

@ahlivehr
Copy link
Contributor

Our certified connector currently doesn't have any issues, but I want to know how to handle an issue if one were to arise.

For example, imagine a certified connector update was submitted via the Partner Center, then it is deployed to the Preview region before being deployed to the other regions. If a very bad issue were found by the connector owner while it is in the Preview region, is there a way to revert the connector update before it continues to be deployed to the other regions? If so, who should be contacted at Microsoft if an issue were found and the deployment needs to be halted and the changes quickly reverted?

Since it takes weeks for normal connector updates and deployments to happen, I'm concerned that any bad issues would take weeks to finally be fixed if we have to follow the normal connector update process. I'm not sure if there's an emergency release process that happens outside the normal deployment process for very urgent connector bug fixes.

The reason I am asking is because we just moved from the old ISV Studio to updating our existing certified connector via the Partner Center. I want to make sure things go smoothly during the transition and we have a fallback plan in case there's an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant