diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md
index 2be902abfa..c4b588f9ca 100644
--- a/windows/deployment/do/mcc-ent-release-notes.md
+++ b/windows/deployment/do/mcc-ent-release-notes.md
@@ -4,158 +4,37 @@ description: Release Notes for Microsoft Connected Cache for Enterprise and Educ
 ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: conceptual
-ms.author: nidos
-author: cmknox
-manager: aaroncz
-ms.reviewer: mstewart
-ms.collection: tier3
+ms.author: lichris
+author: chrisjlin
+manager: naengler
 appliesto: 
 - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
-- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
+- ✅ Supported Linux distributions
 - ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>	
-ms.date: 09/04/2024
+ms.date: 09/27/2024
 ---
 
-<!--
-Remove all the comments in this template before you sign-off or merge to the  main branch.
+# Release Notes for Microsoft Connected Cache for Enterprise and Education (MCCE)
 
-This template provides the basic structure of a Concept article pattern. See the [instructions - Concept](../level4/article-concept.md) in the pattern library.
+This article contains details about the latest releases of MCCE. Since MCCE is a Preview service, some releases may contain breaking changes that will be highlighted as such.
 
-You can provide feedback about this template at: https://aka.ms/patterns-feedback
+## Release v0.1.0 (Public Preview launch)
 
-Concept is an article pattern that defines what something is or explains an abstract idea.
+- Released on **10/17/2024**
+- Contains breaking changes
+- Contains service changes
+- Contains client changes
+- Affects Linux, Windows host machines
 
-There are several situations that might call for writing a Concept article, including:
+### Changenotes
 
-* If there's a new idea that's central to a service or product, that idea must be explained so that customers understand the value of the service or product as it relates to their circumstances. A good recent example is the concept of containerization or the concept of scalability.
-* If there's optional information or explanations that are common to several Tutorials or How-to guides, this information can be consolidated and single-sourced in a full-bodied Concept article for you to reference.
-* If a service or product is extensible, advanced users might modify it to better suit their application. It's better that advanced users fully understand the reasoning behind the design choices and everything else "under the hood" so that their variants are more robust, thereby improving their experience.
-
--->
-
-<!-- 1. H1
------------------------------------------------------------------------------
-
-Required. Set expectations for what the content covers, so customers know the content meets their needs. The H1 should NOT begin with a verb.
-
-Reflect the concept that undergirds an action, not the action itself. The H1 must start with:
-
-* "\<noun phrase\> concept(s)", or
-* "What is \<noun\>?", or
-* "\<noun\> overview"
-
-Concept articles are primarily distinguished by what they aren't:
-
-* They aren't procedural articles. They don't show how to complete a task.
-* They don't have specific end states, other than conveying an underlying idea, and don't have concrete, sequential actions for the user to take.
-
-One clear sign of a procedural article would be the use of a numbered list. With rare exception, numbered lists shouldn't appear in Concept articles.
-
--->
-
-# [\<noun phrase\> concept(s)]
-TODO: Add your heading
-
-<!-- 2. Introductory paragraph
-----------------------------------------------------------
-
-Required. Lead with a light intro that describes what the article covers. Answer the fundamental “why would I want to know this?” question. Keep it short.
-
-* Answer the fundamental "Why do I want this knowledge?" question.
-* Don't start the article with a bunch of notes or caveats.
-* Don’t link away from the article in the introduction.
-* For definitive concepts, it's better to lead with a sentence in the form, "X is a (type of) Y that does Z."
-
--->
-
-[Introductory paragraph]
-TODO: Add your introductory paragraph
-
-<!-- 3. Prerequisites --------------------------------------------------------------------
-
-Optional: Make **Prerequisites** your first H2 in the article. Use clear and unambiguous
-language and use a unordered list format. 
-
--->
-
-## Prerequisites
-TODO: [List the prerequisites if appropriate]
-
-<!-- 4. H2s (Article body)
---------------------------------------------------------------------
-
-Required: In a series of H2 sections, the article body should discuss the ideas that explain how "X is a (type of) Y that does Z":
-
-* Give each H2 a heading that sets expectations for the content that follows.
-* Follow the H2 headings with a sentence about how the section contributes to the whole.
-* Describe the concept's critical features in the context of defining what it is.
-* Provide an example of how it's used where, how it fits into the context, or what it does. If it's complex and new to the user, show at least two examples.
-* Provide a non-example if contrasting it will make it clearer to the user what the concept is.
-* Images, code blocks, or other graphical elements come after the text block it illustrates.
-* Don't number H2s.
-
--->
-
-## [Section 1 heading]
-TODO: add your content
-
-## [Section 2 heading]
-TODO: add your content
-
-## [Section n heading]
-TODO: add your content
-
-<!-- 5. Next step/Related content ------------------------------------------------------------------------ 
-
-Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
-  - For Next step, provide one link to the next step in a sequence. Use the blue box format
-  - For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
-
--->
-
-## Next step
-
-TODO: Add your next step link(s)
-
-> [!div class="nextstepaction"]
-> [Write concepts](article-concept.md)
-
-<!-- OR -->
+- Added new "Outbound egress" and "Volume by Content type" monitoring charts to Azure portal user interface
+- Added ability to create custom monitoring charts under the Metrics tab in the Azure portal user interface
+- Added support for creating both Windows-hosted and Linux-hosted cache nodes under the same MCC Azure resource
+- Added Azure CLI support for programmatic creation and management of MCC Azure resources and cache nodes
+- Added support for unauthenticated proxy and cloud proxy integration
+- Added ability to set each cache node's Update Ring to govern cadence of MCCE container updates
 
 ## Related content
 
-TODO: Add your next step link(s)
-
-- [Write concepts](article-concept.md)
-
-<!--
-Remove all the comments in this template before you sign-off or merge to the main branch.
--->
-
-
-<!-- 6. Next step/Related content ------------------------------------------------------------------------
-
-Optional: You have two options for manually curated links in this pattern: Next step and Related
-content. You don't have to use either, but don't use both. For Next step, provide one link to the
-next step in a sequence. Use the blue box format For Related content provide 1-3 links. Include some
-context so the customer can determine why they would click the link. Add a context sentence for the
-following links.
-
--->
-
-## Next step
-TODO: Add your next step link(s)
-> [!div class="nextstepaction"]
-> [Write concepts](article-concept.md)
-
-<!-- OR -->
-
-## Related content
-TODO: Add your next step link(s)
-- [Write concepts](article-concept.md)
-
-<!--
-Remove all the comments in this template before you sign-off or merge to the 
-main branch.
-
--->
+- [Overview of MCCE](mcc-ent-edu-overview.md)
diff --git a/windows/deployment/do/mcc-ent-support-and-troubleshooting.md b/windows/deployment/do/mcc-ent-support-and-troubleshooting.md
index 2f4b72d936..83c3b59054 100644
--- a/windows/deployment/do/mcc-ent-support-and-troubleshooting.md
+++ b/windows/deployment/do/mcc-ent-support-and-troubleshooting.md
@@ -5,8 +5,8 @@ ms.service: windows-client
 ms.subservice: itpro-updates
 ms.topic: how-to
 manager: naengler
-ms.author: nidos
-author: doshnid
+ms.author: lichris
+author: chrisjlin
 appliesto: 
 - ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
 - ✅ Supported Linux distributions
@@ -38,8 +38,7 @@ For example: "Migrate data from regular tables to ledger tables" or "Create a ne
 
 -->
 
-# "verb * noun"
-TODO: Add your heading
+# Troubleshoot Microsoft Connected Cache for Enterprise and Education (MCCE)
 
 <!-- 2. Introductory paragraph ----------------------------------------------------------
 
@@ -55,65 +54,35 @@ Example: In this article, you will migrate your user databases from IBM Db2 to S
 
 -->
 
-TODO: Add your introductory paragraph
+This article contains instructions on how to troubleshoot different issues you may encounter while using MCCE. These issues are categorized by the task in which they may be encountered. For example, this next section covers troubleshooting [MCC Azure resource creation](mcc-ent-create-resource-and-cache).
 
-<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
+## Troubleshooting Azure resource creation
 
--->
+MCC Azure resource creation can be initiated using either the Azure portal or the Azure CLI command set. If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields.
 
-<!-- 3. Prerequisites --------------------------------------------------------------------
-
-Required: Make Prerequisites the first H2 after the H1. 
-
-* Provide a bulleted list of items that the user needs.
-* Omit any preliminary text to the list.
-* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
-
--->
-
-## Prerequisites
-
-TODO: List the prerequisites
-
-<!-- 4. Task H2s ------------------------------------------------------------------------------
-
-Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
-
-For portal-based procedures, minimize bullets and numbering.
-
-* Each H2 should be a major step in the task.
-* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
-* Don't start with a gerund.
-* Don't number the H2s.
-* Begin each H2 with a brief explanation for context.
-* Provide a ordered list of procedural steps.
-* Provide a code block, diagram, or screenshot if appropriate
-* An image, code block, or other graphical element comes after numbered step it illustrates.
-* If necessary, optional groups of steps can be added into a section.
-* If necessary, alternative groups of steps can be added into a section.
-
--->
-
-## "\<verb\> * \<noun\>"
+## Troubleshooting cache node creation
 TODO: Add introduction sentence(s)
 [Include a sentence or two to explain only what is needed to complete the procedure.]
 TODO: Add ordered list of procedure steps
+
 1. Step 1
 1. Step 2
 1. Step 3
 
-## "\<verb\> * \<noun\>"
+## Troubleshooting cache node deployment
 TODO: Add introduction sentence(s)
 [Include a sentence or two to explain only what is needed to complete the procedure.]
 TODO: Add ordered list of procedure steps
+
 1. Step 1
 1. Step 2
 1. Step 3
 
-## "\<verb\> * \<noun\>"
+## Troubleshooting cache node monitoring
 TODO: Add introduction sentence(s)
 [Include a sentence or two to explain only what is needed to complete the procedure.]
 TODO: Add ordered list of procedure steps
+
 1. Step 1
 1. Step 2
 1. Step 3
@@ -126,22 +95,6 @@ Optional: You have two options for manually curated links in this pattern: Next
 
 -->
 
-## Next step
-
-TODO: Add your next step link(s)
-
-> [!div class="nextstepaction"]
-> [Write concepts](article-concept.md)
-
-<!-- OR -->
-
-## Related content
-
-TODO: Add your next step link(s)
-
-- [Write concepts](article-concept.md)
-
-<!--
-Remove all the comments in this template before you sign-off or merge to the main branch.
--->
+## Filing a support request
 
+TODO: Add steps for filling out a CSS ticket.