Skip to content
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

Generic credentials for outlook 365 and route attachments from outlook 365 emails to a azure storage account #20388

Closed
saikothakapu opened this issue Aug 23, 2021 · 4 comments
Assignees
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)

Comments

@saikothakapu
Copy link

Currently , In one of our project we created a dashboard which is scripted in python and all the code is running in a local machine. In this dashboard, it consumes data from excel files which are shared as attachments in an outlook personal email.
For connecting to outlook emails and fetch attached excel files, we are using personal credentials which we wanted to avoid.
Can someone please help us if there is a way to create a generic outlook account with generic credentials and later route all the attachments to a azure storage blob for storing through python scripting. Appreciate your responses.

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Aug 23, 2021
@YalinLi0312
Copy link
Member

Thanks for the feedback, we'll investigate asap.

@YalinLi0312 YalinLi0312 added the Storage Storage Service (Queues, Blobs, Files) label Aug 23, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 23, 2021
@YalinLi0312 YalinLi0312 added the Service Attention Workflow: This issue is responsible by Azure service team. label Aug 23, 2021
@ghost
Copy link

ghost commented Aug 23, 2021

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

Issue Details

Currently , In one of our project we created a dashboard which is scripted in python and all the code is running in a local machine. In this dashboard, it consumes data from excel files which are shared as attachments in an outlook personal email.
For connecting to outlook emails and fetch attached excel files, we are using personal credentials which we wanted to avoid.
Can someone please help us if there is a way to create a generic outlook account with generic credentials and later route all the attachments to a azure storage blob for storing through python scripting. Appreciate your responses.

Author: saikothakapu
Assignees: -
Labels:

Storage, question, Service Attention, customer-reported

Milestone: -

@ghost ghost added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Aug 23, 2021
@mccoyp
Copy link
Member

mccoyp commented Aug 23, 2021

Hi @saikothakapu, thank you for opening an issue! The Storage team has been looped in to help you with anything on the SDK front, but it sounds like your question is mostly about creating a certain kind of Outlook account. To determine how we can best help, it would be great to know if you're having any Azure SDK-specific issues, or if this is Outlook-specific. It may be a good idea to contact support for Outlook or ask a forum question if you haven't already.

@saikothakapu
Copy link
Author

thanks @mccoyp , I have posted the question in outlook forum.

azure-sdk pushed a commit to azure-sdk/azure-sdk-for-python that referenced this issue Sep 13, 2022
Review request for Microsoft.ContainerService to add version 2022-08-02-preview (Azure#20487)

* Adds base for updating Microsoft.ContainerService from version preview/2022-07-02-preview to version 2022-08-02-preview

* Updates readme

* Updates API version in new specs and examples

* sync changes from PR#19592 & PR#20145 (Azure#20402)

* update readme & remove fleets (Azure#20388)

* AKS agent pool properties add AgentPoolWindowsProfile and DisableOutboundNAT (Azure#20407)

* AKS agent pool properties add AgentPoolWindowsProfile and DisableOutboundNAT

* Change disableOutboundNAT to disableOutboundNat because of ARM format; Improve description.

* Improve description

* Added guardrails profile to specs (Azure#20171)

* added guardrails profile to specs

* linter fix

* added x-ms-enum

* added guardrails definitions for versions route

* linter fix, added custom word

* fix

* typo fix

* fix for example

* added object type

* added object type

* removed data field

* changed descriptions

* *

* add "Mariner" for AKS os sku (Azure#20420)

* add KubeProxyConfig to AKS NetworkProfile (Azure#20446)

* add KubeProxyConfig to AKS NetworkProfile

* remove extra comma, type: integer for *Seconds

* add custom words

* prettier

* follow camel case ARM guidance

* 2nd camel case standard

* feat: add rest api spec for ip-based lb (Azure#20392)

* fix LroLocationHeader (Azure#20491)

* fix ProvisioningStateValidation (Azure#20490)

* Removed guardrailsVersions route, added guardrails profice to MC properties (Azure#20625)

* removed guardrails-versions route, added guardrails profice to MC properties

* removed unsued file for guardrails versions, removed unused custom word

Co-authored-by: Shiqian Tao <[email protected]>
Co-authored-by: rsamigullin <[email protected]>
Co-authored-by: Ace Eldeib <[email protected]>
Co-authored-by: Matt Stam <[email protected]>
Co-authored-by: Qi Ni <[email protected]>
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

5 participants