-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mistake of default environment variables about O365 Data Connector #11216
Comments
Hi @NobufumiMurata, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks! |
Hi @v-sudkharat , This URL hosts package of function apps source and "run.ps1" in this package was written with the URL without a slash. I think this difference of describing is the root cause of this matter. Could you confirm that please. |
Hi @NobufumiMurata, Yes correct, the "/" cause the script failure. Thanks! |
Hi @v-sudkharat I confirmed the new code and I notice that there are two modifications.
Could you confirm that again? |
Hey @NobufumiMurata, And run it manually. Thanks! |
Hi @v-sudkharat Thank you for your kind response. |
Describe the bug
The environment variable of the default LoginEndpoint of the template used in the "Deploy the Azure Function App" procedure has a "/" at the end like "https://login.microsoftonline.com/", but if this slash is added, the following error occurs when the function app is executed.
I have confirmed at the error in run.ps1 with the following code, and it is verified with a URL without a slash as shown in "https://login.microsoftonline.com".
When I erased the trailing slash in that environment variable, the function app now exited gracefully.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The function app run correctly with default settings using "Deploy to Azure" button
Screenshots
N/A
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Nothing in particular
The text was updated successfully, but these errors were encountered: