Azure Functions And Conflicting Package References

In the day of the internet, you expect there is documentation or someone else out there that has run into the same issue as you. This is the first time there seems be no clear answer the problem. In a recent project I’ve been working on we have packages from ASP.Net Core to do Authorization <PackageReference Include="Microsoft.AspnetCore.Authentication" Version="7.0.2"> Using this package reference causes the Azure functions to not boot and perform tasks as they usually would. Some suspected causes are Mismatched versions of .Net Core between the project and Azure functions Other unknown dependency errors The reason for moving this to a separate service and out of our API is to make it modular and fetch our specific data from anywhere in the project. Because of this issue, I had to create a workaround and create two fetch services one specific to the internal project that did not use that particular library and one specific to the external api that uses the correct authorization library. I would like to eventually get a better solution for this so if you come across this problem, feel free to send me a DM on Twitter @josephk1551