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

[QUERY] Azure.Communication.Email Inline Attachments #47691

Open
jacobjohnston opened this issue Dec 31, 2024 · 1 comment
Open

[QUERY] Azure.Communication.Email Inline Attachments #47691

jacobjohnston opened this issue Dec 31, 2024 · 1 comment
Labels
Client This issue points to a problem in the data-plane of the library. Communication - Email 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.

Comments

@jacobjohnston
Copy link

Library name and version

Azure.Communication.Email 1.1.0-beta2

Query/Question

I was trying to use inline attachments in Azure.Communications.Email, but the steps that are officially documented did not work.

It didn't take long to discover that was because I needed Azure.Communication.Email 1.1+, but only 1.0 is out of Prerelease.

Is there any plan/milestone for when 1.1 will be moved out of beta? It hasn't had any commits in a number of months. Anecdotally, the beta seems to be working perfectly fine for inline attachments.

Environment

No response

@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. Communication 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. labels Dec 31, 2024
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @abhishesingh-msft @abhiucandoit @adamtuck-msft @adriansynal-msft @AikoBB @ajaych-ms @ajitht-msft @akania @alcail @alexandra142 @AliRafiee @alkwa-msft @allchiang-msft @allenplusplus @AlonsoMondal @alvinjiang-msft @amagginetti @amandaong @amariwest-msft @amatukmolina @AmeliaHeMS @AMollis @andboyer @andrewjhopkins @angelcaz-msft @angellan-msft @angiurgiu @anjulgarg @ankeshni @ankitamm @ankitarorabit @anmolbohra97 @ansrin @antonsamson-msft @anujb-msft @anujissarMS @arifibrahim4 @arifsaikat-microsoft @armandliv @armansabaa @arupdutta-msft @ashwinder @BalajiUmmadisetti @beltr0n @besh2014 @bga-msft @bharat-kalyan-namburi @bobserr @boris-bazilevskiy @brpiment @bterlson @calvinkwtang @carlosalm-msft @carocao-msft @cemateia @chengyuanlai-msft @cheukchuen @CHILIU-MSFT @chriswhilar @chrwhit @claireoberg-msft @cn0151 @cochi2 @csandjon @dailam-msft @danielav7 @danielgerlag @danielortega-msft @dassabya15 @DaybreakQuip @ddouglas-msft @devwolf1 @dinazavyr @dmceachernmsft @DominikMe @dvillasenor-msft @dzeliar @ealejandrootalvaro @edwardlee-msft @elavarasidc @emlynmac @enguerrandb-msft @enricohuang @ericasp16 @eriwang-msft @fangchen0601 @fanruisun @FarhadJabiyev @FerOsorio @fhaghbin-msft @fizampou @fuyan2024 @gaobob-msft @garchiro7 @Gemakk @genevievetok @gfeitosa-msft @glorialimicrosoft @GoWang @grangasamy-msft @grigoryk @guoqing2023 @hansung-msft @hrazi @huachuandeng @HuangXin-MS @iaulakh @ihuseynov-msft @ikumarapeli-msft @ilyapaliakou-msft @imikemo @jadacampbell @jakublehotsky @JamesBurnside @jamescadd @jannovak-msft @jdebroin-msft @jethier-msft @JianpingChen @jimchou-dev @jiminwen-msft @jiriburant @jirisofka @jjsanchezms @Joeleniqs @jorge-beauregard @josecomboni @JoshuaLai @jowang-msft @jpeng-ms @jrathor @jsaurezlee-msft @juancamilor @juntuchen-msft @jutik0 @kagbakpem @khannavikas @kieraniles-msft @ktimofejev-msft @kurtzeborn @Leah-Xia-Microsoft @lei-msft @lisaleehan @LoadLibrary @lsundaralingam @LuChen-Microsoft @lucianopa-msft @magesh-ms @mannyovena @marche0133 @mariusu-msft @matthohn-msft @maximrytych-ms @mayssamm @megheshpatil @mgamis-msft @miguhern @mikehang-msft @MilanKaur-01 @minnieliu @minwoolee-msft @mjafferi-msft @mmpowers-mi @msft-qifan @MSFTFox @namratasimha-msft @natekimball-msft @NathanJBennett @navali-msft @nemofei11 @nikithauc @nikuklic @ninikasharma @nmaredia @nmurav @nostojicMs @osaghaso @palatter @paolamvhz @Paresh-Arvind-Patil @paveldostalms @pavelprystinka @pereiralex @pgrandhi @phermanov-msft @pkestikar @pohtsng @poorva-MSFT @prabhjot-msft @prasadker @priyankaaprakash @rajasekaran2003 @rajat-rastogi @rajuanitha88 @ralphgabrinao @ramneettung-msft @raosanat @rasinive @RezaJooyandeh @rkprasad-ks @rorezende @ryturn757 @rzdor @sacheu @Saisang @SamuelSA @sankum-msft @sarkar-rajarshi @satyakonmsft @Scott-Leong @Shamkh @sharifrahaman @ShaunaSong @shirleyqin-msft @shwali-msft @slpavkov @sofiar-msft @soricos85 @sorrego-msft @sphenry @stefang931 @subhasan @swagatmishra2007 @tadam-msft @tariqzafa700 @tomaschladek @tonyliu43361 @tophpalmer @usvoyager @v-durgeshs @v-mbarad-msft @v-pivamshi @v-shazilms @v-vdharmaraj @vaibhavjain-msft @vamoskal @vhuseinova-msft @VikramDhumal @vikrampraveen @viniciusl-msft @vinoPuzzle @vivekmore-msft @vriosrada-msft @wangrui-msft @waynemo @whisper6284 @williamzhao87 @xixian73 @xumo-95 @xxwikkixx @yassirbisteni @yogeshmo @ypradhan-msft @zeyingguo1991 @zhengni-msft @zihzhan-msft.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Communication - Email 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.
Projects
None yet
Development

No branches or pull requests

2 participants