Merge pull request #16325 from alkohli/13azl-reb

Added renaming doc

Author: Jill Grant

azure-local/TOC.yml

@@ -7,6 +7,8 @@ items:
     href: overview.md
   - name: What's new in Azure Local? 
     href: whats-new.md
+  - name: Renaming to Azure Local
+    href: rename-to-azure-local.md
   - name: Release notes
     items:
     - name: Release information

azure-local/rename-to-azure-local.md

@@ -0,0 +1,100 @@
+---
+title: Renaming Azure Stack HCI to Azure Local
+description: This article provides the renaming information for Azure Stack HCI to Azure Local.
+author: alkohli
+ms.author: alkohli
+ms.topic: conceptual
+ms.service: azure-stack-hci
+ms.date: 11/12/2024
+---
+
+# New name for Azure Stack HCI
+
+Azure Stack HCI is now a part of Azure Local. Microsoft has renamed Azure Stack HCI to Azure Local to communicate a single brand that unifies the entire distributed infrastructure portfolio. This article describes Azure Local as the new name for Azure Stack HCI and answers commonly asked questions related to this rebranding.
+
+## No interruptions to usage or service
+
+If you're currently using Azure Stack HCI today or previously deployed Azure Stack HCI in your organizations, you can continue to use the service without interruption. All existing deployments, configurations, and integrations continue to function as they do today without any action from you.
+
+All features and capabilities are still available in the product. Pricing, licensing, terms, service-level agreements, product certifications, and support remain the same. Details on pricing and what’s included are available on the [Pricing page](https://aka.ms/azloc-pricing).
+
+To make the transition seamless, all existing sign in URLs, APIs, and PowerShell cmdlets stay the same, as do developer experiences and tooling.
+
+<!--For self-service support, look for the topic path of Azure Local. - verify with CSS -->
+
+The product name is changing, and features are now branded as Azure Local instead of Azure Stack HCI. If you're updating the name to Azure Local in your own content or experiences, see [Naming changes and exceptions](#naming-changes-and-exceptions).
+
+## Naming changes and exceptions
+
+### Product name
+
+Here are the naming changes:
+
+- Azure Local is the new name for Azure Stack HCI. Azure Local doesn’t have an acronym.
+- Azure Stack HCI clusters are renamed as Azure Local instances.
+- Azure Stack HCI servers are renamed as Azure Local machines.
+
+### Logo/icon
+
+Azure Local product icons continue to be the same as those for Azure Stack HCI.
+
+### What names aren't changing?
+
+The following table lists what isn't impacted by the rename.
+
+| Components/Terms | Details |
+|---------------------|---------|
+| Azure Stack HCI APIs/namespace  | No breaking changes were made to Azure Stack HCI APIs/namespaces and won’t require you to update code. |
+| Azure Stack HCI resource provider        | The `Microsoft.AzureStackHCI` resource provider name remains the same. |
+| Azure Stack HCI PowerShell cmdlets | The Azure Stack HCI PowerShell cmdlets remain the same. |
+| Azure Stack HCI CLI | The Azure CLI commands for Azure Stack HCI and Arc VM management continue to remain the same.  |
+| Azure Stack HCI OS  | The Azure Stack HCI Operating System (OS) which is a component of the Azure Local, will remain the same. |
+| Azure Stack HCI OEM License | The license name remains the same. |
+
+In addition, documentation for older versions of Azure Stack HCI, for example, 22H2 only, will continue to reference Azure Stack HCI and not reflect the name change.
+
+## Frequently asked questions
+
+### When is the name change happening?
+
+The name change across the text strings in Microsoft experiences such as product page, pricing page, and Azure Stack HCI and AKS-HCI Learn pages will occur on November 19, 2024. The names in the text strings in the Azure portal will be completed by early 2025.
+
+### Why is the name being changed?
+
+As part of our ongoing commitment to simplify access experiences for everyone, the renaming of Azure Stack HCI to Azure Local is designed to make it easier to use and navigate the unified and expanded capabilities of Azure Local.
+
+The Azure Local name more accurately represents the entire unified distributed infrastructure portfolio.
+
+### Where can I manage Azure Local?
+
+You can manage Azure Local in the [Azure portal](https://portal.azure.com).
+
+### Is Azure Stack HCI going away?
+
+No, only the name Azure Stack HCI is going away. The product capabilities remain the same and continue to expand.
+
+### Are licenses changing? Are there any changes to pricing?
+
+No. Prices, terms, and service level agreements (SLAs) remain the same.
+
+The Azure billing meters for Azure Stack HCI will be renamed with meter ID updates. This change will be completed by early 2025. The meter name and ID changes don’t affect prices. However, you might notice some changes in how your Azure consumption is shown on your invoice, price sheet, API, usage details file, and **Cost Management + Billing** experiences.
+
+### Are PowerShell cmdlets and Azure CLI commands being renamed?
+
+No. Both the PowerShell cmdlets and Azure CLI commands for Arc VM management and for Azure Stack HCI cluster, service, and management continue to remain the same.
+
+### How and when are customers being notified?
+
+The name changes will be publicly announced on November 19, 2024.
+
+Banners, alerts, and message center posts will notify users of the name change. The change will also be displayed on the Azure Local overview page in the Azure portal, Azure Stack HCI Catalog pages, and Microsoft Learn.
+
+### What if I use the Azure Local name in my content?
+
+We'd like your help spreading the word about the name change and implementing it in your own experiences. If you're a content creator, author of internal documentation for IT or Azure Local IT admin, independent software vendor, or Microsoft partner, you can use the naming guidance outlined in this document to make the name change in your content and product experiences.
+
+## Next steps
+
+- [Learn more about Azure Local](./overview.md)
+- [Get started using Azure Local](./deploy/deployment-introduction.md)
+