Update Service-Fabric-70CU4-releasenotes.md

release_notes/Service-Fabric-70CU4-releasenotes.md

@@ -56,6 +56,8 @@ Service Fabric versions below the Service Fabric 7.0 Third Refresh Release (Wind
 | **Windows .NET SDK** | **Bug** | SF Runtime SDK setup was blocked when running as SYSTEM. | **Impact**: SDK setup in some automated environments runs as SYSTEM, which cannot set Powershell execution policy and this was required to run setup. <br> **Fix**: A parameter has been added to the runtime installation exe: /SkipPSExecutionPolicy, which bypasses setting Powershell execution policy. |
 | **Windows .NET SDK** | **Bug** | Runtime SDK installation wedges when runtime files have only been partially wiped. | **Impact**: In some cases the SF SDK becomes partially uninstalled which leaves behind some key components that cause the subsequent reinstallation to self-identify as already installed which blocks reinstallation. <br> **Fix**: SDK SF runtime installer now autoresolves corrupted runtime installations where registry entries remain but files have been removed, in order to unblock installation of the new version. <br> **Workaround**: Manually delete the Service Fabric 'Add-Remove Programs' registry uninstall entry, as well as the HKLM Software entry for Service Fabric. |
 | **Windows 7.0.470.9590** | **Bug** | Fabric Upgrade Service keeps retrying application upgrade after rollback. | **Impact**: When an operation is currently running and a new one gets queued for the same resource, the new operation never gets added to the operations map. If the second operation rolls back it will keep retrying until it times out instead of failing. <br> **Fix**: Update operation map with new upgrade. <br> **Workaround**: Manually restart Fabric Upgrade Service primary replica. |
+| **Windows 7.0.470.9590** | **Bug** | Support logs and files are not uploaded to Azure Storage from FIPS enabled machines. | **Impact**: No support logs are uploaded by FabricDCA process from FIPS enabled machines. <br> **Fix**: FabricDCA now configures the Azure Storage API it uses for uploading to Azure Storage to not use the default MD5 hashing algorithm which is not compliant with FIPS. <br> **Workaround**: Disable FIPS. |
+
 
 ## Repositories and Download Links