What is Sitecore Managed Cloud?
Coming from a xDB Cloud point of view, when I hear Sitecore Managed Cloud, I think of just xConnect and Processing and Reporting hosting.
However, on the surface it appears to be a full Azure XP1 Subscription, but I am confused on what they are actually providing as a service. Is Sitecore actually managing the entire Azure subscription for a full Sitecore site? Or am I reading this completely wrong?
What is Sitecore Managed Cloud and what services does it provide to the client?
deployment xdb-cloud
asked yesterday
Pete NavarraPete Navarra
11.2k2675
add a comment |
Coming from a xDB Cloud point of view, when I hear Sitecore Managed Cloud, I think of just xConnect and Processing and Reporting hosting.
However, on the surface it appears to be a full Azure XP1 Subscription, but I am confused on what they are actually providing as a service. Is Sitecore actually managing the entire Azure subscription for a full Sitecore site? Or am I reading this completely wrong?
What is Sitecore Managed Cloud and what services does it provide to the client?
deployment xdb-cloud
asked yesterday
Pete NavarraPete Navarra
11.2k2675
add a comment |
Coming from a xDB Cloud point of view, when I hear Sitecore Managed Cloud, I think of just xConnect and Processing and Reporting hosting.
However, on the surface it appears to be a full Azure XP1 Subscription, but I am confused on what they are actually providing as a service. Is Sitecore actually managing the entire Azure subscription for a full Sitecore site? Or am I reading this completely wrong?
What is Sitecore Managed Cloud and what services does it provide to the client?
deployment xdb-cloud
asked yesterday
Pete NavarraPete Navarra
11.2k2675
Coming from a xDB Cloud point of view, when I hear Sitecore Managed Cloud, I think of just xConnect and Processing and Reporting hosting.
However, on the surface it appears to be a full Azure XP1 Subscription, but I am confused on what they are actually providing as a service. Is Sitecore actually managing the entire Azure subscription for a full Sitecore site? Or am I reading this completely wrong?
What is Sitecore Managed Cloud and what services does it provide to the client?
deployment xdb-cloud
deployment xdb-cloud
asked yesterday
Pete NavarraPete Navarra
11.2k2675
asked yesterday
Pete NavarraPete Navarra
11.2k2675
asked yesterday
Pete NavarraPete Navarra
11.2k2675
asked yesterday
Pete NavarraPete Navarra
11.2k2675
asked yesterday
Pete NavarraPete Navarra
11.2k2675
11.2k2675
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Sitecore Managed Cloud provides a hosting service for the infrastructure associated with Sitecore. The entire topology is owned and "managed" by Sitecore under their Azure Subscription. Generally, the definition of this topology is based on the agreement between the client and Sitecore. From what I have seen, this usually consists of 3 environments (DEV (XP Single), STG (XP Small), PRD (XP [based-on-traffic]). Keep in mind, once you get to scale, the size of the topology usually just drives [expected] CD count.
From an ownership perspective, the contract usually includes some level of monitoring or support, and Sitecore is responsible for security/access management; when someone needs access to the environment, I typically have to submit a support ticket with the MC Contract Identifier and list of emails addresses to have them added.
From a support perspective, the line grays a little bit. I am a contributor for the MC instance that I worked on, which means I have access to do everything except manage access. I have been able to redo the topology to fit my client's needs (e.g. switch to an elastic pool, increase CM tier, etc.). Generally speaking, the partner plays a large role in supporting the applications, as they are responsible for adding, breaking, and fixing the code. If there are infrastructure issues, then a ticket can be opened with Sitecore to have them examine it. However, it might be faster to figure out and resolve the issue yourself; it depends on the severity of the issue and the SLA on the MC Contract.
Ultimately, the contracts are usually based on annual Azure Spend (billed monthly). The client has a spending limit, and if they go over that (unforeseen scaling === more CDs === more money), they can be charged overages. Keep this in mind when making or suggestions any infrastructure changes to the client.
Ultimately, Sitecore is really just providing a hosting platform, and the support model ends up being along the same lines as a standard Sitecore + implementation partner implementation.
edited 8 hours ago
Pete Navarra
11.2k2675
answered yesterday
BicBic
1963
New contributor
Bic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "664"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f17678%2fwhat-is-sitecore-managed-cloud%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sitecore Managed Cloud provides a hosting service for the infrastructure associated with Sitecore. The entire topology is owned and "managed" by Sitecore under their Azure Subscription. Generally, the definition of this topology is based on the agreement between the client and Sitecore. From what I have seen, this usually consists of 3 environments (DEV (XP Single), STG (XP Small), PRD (XP [based-on-traffic]). Keep in mind, once you get to scale, the size of the topology usually just drives [expected] CD count.
From an ownership perspective, the contract usually includes some level of monitoring or support, and Sitecore is responsible for security/access management; when someone needs access to the environment, I typically have to submit a support ticket with the MC Contract Identifier and list of emails addresses to have them added.
From a support perspective, the line grays a little bit. I am a contributor for the MC instance that I worked on, which means I have access to do everything except manage access. I have been able to redo the topology to fit my client's needs (e.g. switch to an elastic pool, increase CM tier, etc.). Generally speaking, the partner plays a large role in supporting the applications, as they are responsible for adding, breaking, and fixing the code. If there are infrastructure issues, then a ticket can be opened with Sitecore to have them examine it. However, it might be faster to figure out and resolve the issue yourself; it depends on the severity of the issue and the SLA on the MC Contract.
Ultimately, the contracts are usually based on annual Azure Spend (billed monthly). The client has a spending limit, and if they go over that (unforeseen scaling === more CDs === more money), they can be charged overages. Keep this in mind when making or suggestions any infrastructure changes to the client.
Ultimately, Sitecore is really just providing a hosting platform, and the support model ends up being along the same lines as a standard Sitecore + implementation partner implementation.
edited 8 hours ago
Pete Navarra
11.2k2675
answered yesterday
BicBic
1963
New contributor
Bic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Sitecore Managed Cloud provides a hosting service for the infrastructure associated with Sitecore. The entire topology is owned and "managed" by Sitecore under their Azure Subscription. Generally, the definition of this topology is based on the agreement between the client and Sitecore. From what I have seen, this usually consists of 3 environments (DEV (XP Single), STG (XP Small), PRD (XP [based-on-traffic]). Keep in mind, once you get to scale, the size of the topology usually just drives [expected] CD count.
From an ownership perspective, the contract usually includes some level of monitoring or support, and Sitecore is responsible for security/access management; when someone needs access to the environment, I typically have to submit a support ticket with the MC Contract Identifier and list of emails addresses to have them added.
From a support perspective, the line grays a little bit. I am a contributor for the MC instance that I worked on, which means I have access to do everything except manage access. I have been able to redo the topology to fit my client's needs (e.g. switch to an elastic pool, increase CM tier, etc.). Generally speaking, the partner plays a large role in supporting the applications, as they are responsible for adding, breaking, and fixing the code. If there are infrastructure issues, then a ticket can be opened with Sitecore to have them examine it. However, it might be faster to figure out and resolve the issue yourself; it depends on the severity of the issue and the SLA on the MC Contract.
Ultimately, the contracts are usually based on annual Azure Spend (billed monthly). The client has a spending limit, and if they go over that (unforeseen scaling === more CDs === more money), they can be charged overages. Keep this in mind when making or suggestions any infrastructure changes to the client.
Ultimately, Sitecore is really just providing a hosting platform, and the support model ends up being along the same lines as a standard Sitecore + implementation partner implementation.
edited 8 hours ago
Pete Navarra
11.2k2675
answered yesterday
BicBic
1963
New contributor
Bic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Sitecore Managed Cloud provides a hosting service for the infrastructure associated with Sitecore. The entire topology is owned and "managed" by Sitecore under their Azure Subscription. Generally, the definition of this topology is based on the agreement between the client and Sitecore. From what I have seen, this usually consists of 3 environments (DEV (XP Single), STG (XP Small), PRD (XP [based-on-traffic]). Keep in mind, once you get to scale, the size of the topology usually just drives [expected] CD count.
From an ownership perspective, the contract usually includes some level of monitoring or support, and Sitecore is responsible for security/access management; when someone needs access to the environment, I typically have to submit a support ticket with the MC Contract Identifier and list of emails addresses to have them added.
From a support perspective, the line grays a little bit. I am a contributor for the MC instance that I worked on, which means I have access to do everything except manage access. I have been able to redo the topology to fit my client's needs (e.g. switch to an elastic pool, increase CM tier, etc.). Generally speaking, the partner plays a large role in supporting the applications, as they are responsible for adding, breaking, and fixing the code. If there are infrastructure issues, then a ticket can be opened with Sitecore to have them examine it. However, it might be faster to figure out and resolve the issue yourself; it depends on the severity of the issue and the SLA on the MC Contract.
Ultimately, the contracts are usually based on annual Azure Spend (billed monthly). The client has a spending limit, and if they go over that (unforeseen scaling === more CDs === more money), they can be charged overages. Keep this in mind when making or suggestions any infrastructure changes to the client.
Ultimately, Sitecore is really just providing a hosting platform, and the support model ends up being along the same lines as a standard Sitecore + implementation partner implementation.
edited 8 hours ago
Pete Navarra
11.2k2675
answered yesterday
BicBic
1963
New contributor
Bic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Sitecore Managed Cloud provides a hosting service for the infrastructure associated with Sitecore. The entire topology is owned and "managed" by Sitecore under their Azure Subscription. Generally, the definition of this topology is based on the agreement between the client and Sitecore. From what I have seen, this usually consists of 3 environments (DEV (XP Single), STG (XP Small), PRD (XP [based-on-traffic]). Keep in mind, once you get to scale, the size of the topology usually just drives [expected] CD count.
From an ownership perspective, the contract usually includes some level of monitoring or support, and Sitecore is responsible for security/access management; when someone needs access to the environment, I typically have to submit a support ticket with the MC Contract Identifier and list of emails addresses to have them added.
From a support perspective, the line grays a little bit. I am a contributor for the MC instance that I worked on, which means I have access to do everything except manage access. I have been able to redo the topology to fit my client's needs (e.g. switch to an elastic pool, increase CM tier, etc.). Generally speaking, the partner plays a large role in supporting the applications, as they are responsible for adding, breaking, and fixing the code. If there are infrastructure issues, then a ticket can be opened with Sitecore to have them examine it. However, it might be faster to figure out and resolve the issue yourself; it depends on the severity of the issue and the SLA on the MC Contract.
Ultimately, the contracts are usually based on annual Azure Spend (billed monthly). The client has a spending limit, and if they go over that (unforeseen scaling === more CDs === more money), they can be charged overages. Keep this in mind when making or suggestions any infrastructure changes to the client.
Ultimately, Sitecore is really just providing a hosting platform, and the support model ends up being along the same lines as a standard Sitecore + implementation partner implementation.
edited 8 hours ago
Pete Navarra
11.2k2675
answered yesterday
BicBic
1963
New contributor
Bic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 8 hours ago
Pete Navarra
11.2k2675
edited 8 hours ago
Pete Navarra
11.2k2675
edited 8 hours ago
Pete Navarra
11.2k2675
11.2k2675
answered yesterday
BicBic
1963
New contributor
Bic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
BicBic
1963
answered yesterday
BicBic
1963
1963
New contributor
Bic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Bic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Bic is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Sitecore Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f17678%2fwhat-is-sitecore-managed-cloud%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
