Merge pull request #280808 from MicrosoftDocs/main

7/15 11:00 AM IST Publish

Author: PhilKang0704

articles/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc.md

@@ -7,7 +7,7 @@ manager: jsuri
 ms.topic: quickstart
 ms.services: azure-arc
 ms.subservice: azure-arc-scvmm
-ms.date: 07/01/2024
+ms.date: 07/11/2024
 ms.custom: references_regions
 
 # Customer intent: As a VI admin, I want to connect my VMM management server to Azure Arc.
@@ -126,7 +126,10 @@ If for any reason, the appliance creation fails, you need to retry it. Run the c
  ./resource-bridge-onboarding-script.ps1 -Force -Subscription <Subscription> -ResourceGroup <ResourceGroup> -AzLocation <AzLocation> -ApplianceName <ApplianceName> -CustomLocationName <CustomLocationName> -VMMservername <VMMservername>
 ```
 
-### Retry command - Linux
+>[!Note]
+>You can find the values for *Subscription*, *ResourceGroup*, *Azlocation*, *ApplianceName*, *CustomLocationName*, and *VMMservername* parameters from the onboarding script.
+
+ ### Retry command - Linux
 
 If for any reason, the appliance creation fails, you need to retry it. Run the command with ```--force``` to clean up and onboard again.
 

articles/mysql/concepts-version-policy.md

@@ -77,7 +77,7 @@ __Azure MySQL 5.7 Deprecation Timelines__
 |Extended support for Azure Database for MySQL v5.7|	September 2025|	September 2024|
 
 > [!NOTE]  
-> We initially planned to stop the creation of new Azure Database for MySQL version 5.7 instances via CLI and Portal after April 2024. However, after further review and customer feedback, we have decided to delay this action. The specific date for discontinuing the creation of new MySQL 5.7 instances is currently under review and remains 'To Be Decided'. This change reflects our commitment to accommodating customer needs and providing flexibility during the transition. We value your feedback and encourage ongoing communication as we navigate these changes.
+> We initially planned to stop the creation of new Azure Database for MySQL version 5.7 instances via CLI and Portal after April 2024. However, after further review and customer feedback, we have decided to delay this action. The specific date for discontinuing the creation of new MySQL 5.7 instances is currently under review and remains 'To Be Decided'. This change reflects our commitment to accommodating customer needs and providing flexibility during the transition. Don't hesitate to let us know if you have any concerns about the Azure Database For MySQL Flexible Server extended support for MySQL 5.7 by email us at [Ask Azure DB For MySQL](mailto:[email protected]), we value your feedback and encourage ongoing communication as we navigate these changes.
 
 ### FAQs
 

articles/operator-nexus/howto-upgrade-nexus-fabric.md

@@ -79,6 +79,8 @@ Follow the recommended sequence for device upgrades, addressing any failures man
 
 - Verify all devices are configured and synchronized.
 
+- Ensure that there is at least **3GB of available disk space** within the directory `/mnt` to proceed with NNF device upgrade .
+
 Upgrade individual devices with the following command:
 
 ```Azure CLI
@@ -128,4 +130,6 @@ Check the version status of all devices and the fabric with AZCLI commands.
 
 ### **Known issues**
 
-Create the EOS image directory manually at `/mnt/nvram/nexus/eosimages` if it's missing. This is especially important for environments built from older NF versions. A fix is forthcoming in a future release.
+1. Create the EOS image directory manually at `/mnt/nvram/nexus/eosimages` if it is missing. This is especially important for environments built from older NF versions.
+2. NNF device upgrades fail when the available disk space within the directory `/mnt` is less than 3GB. Perform a manual clean up to free up disk space within the NNF device and then retry the upgrade operation.
+