Azure SDKs Upgrade and Dependency Management

All Submissions:

---

• [YES] Have you followed our code review guidelines?
• [YES] Have you added an explanation of what your changes do and why you'd like us to include them?
• [YES] I have updated the documentation accordingly.
• [NA] I have added tests to cover my changes.
• [YES] All new and existing tests passed.
• [YES] My code follows the code style of this project.
• [NO] I ran lint checks locally prior to submission.

What is the current behavior?

---

• Old version of Azure SDKs are used in service.
• Versions of dependencies which are common across all OSDU services are not consistent/same in all OSDU services.

Issue: https://dev.azure.com/msazure/One/_workitems/edit/8708950

What is the new behavior?

---

• All Azure SDKs are upgraded to latest stable version.
• Common dependencies are inherited from core-lib-azure as managed dependencies. This will make sure that version info of those dependencies are inherited from core-lib-azure. All OSDU services using same version of core-lib-azure will automatically use same versions for all those dependencies.
• Changes to support new cosmos-store.

Does this introduce a breaking change?

---

• [NO]

Any relevant logs, error output, etc?

---

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)

Other information

---

provider/legal-azure/pom.xml

@@ -33,7 +33,7 @@
         <azure.appservice.plan></azure.appservice.plan>
         <azure.appservice.appname></azure.appservice.appname>
         <azure.appservice.subscription></azure.appservice.subscription>
-        <osdu.azurecore.version>0.0.37</osdu.azurecore.version>
+        <osdu.azurecore.version>0.0.40</osdu.azurecore.version>
     </properties>
 
     <dependencyManagement>