[AREA]: Process inbound goods

[ngump]

Contact details

ngump@microsoft.com

Organization type

Microsoft employee

End-to-end business process

Inventory to deliver

Specify the business process area name for the article.

Process inbound goods

Enter any additional comments or information you want us to know about this business process area.

Looking for help on this business process area.

Specify the date you expect the article to be completed and ready for review.

09/30/2023

Code of Conduct

• I agree to follow this project's Code of Conduct

[louxblick]

Please remove me from this GitHub project. I do no know why I am receiving these messages. Regards. -Lou [cid:5abe376d-7d46-47b5-969e-01729586c94b] Lou Blick Sr. Cloud Solution Architect, Azure Digital & App Innovation Microsoft Federal | Customer Success Unit [cid:f3868f23-0262-40f8-b6ca-34736665ce4c] W: 202-831-6416<tel:202-831-6416> | M: 202.669.2371<tel:202.669.2371> | E: ***@***.******@***.***> ***@***.***?anonymous&ep=signature>

…

________________________________ From: Nicole Gump ***@***.***> Sent: Monday, August 28, 2023 10:12 AM To: microsoft/dynamics365patternspractices ***@***.***> Cc: Subscribed ***@***.***> Subject: [microsoft/dynamics365patternspractices] [AREA]: Process inbound goods (Issue #102) Contact details ***@***.******@***.***> Organization type Microsoft employee End-to-end business process Inventory to deliver Specify the business process area name for the article. Process inbound goods Enter any additional comments or information you want us to know about this business process area. Looking for help on this business process area. Specify the date you expect the article to be completed and ready for review. 09/30/2023 Code of Conduct * I agree to follow this project's Code of Conduct — Reply to this email directly, view it on GitHub<#102> or unsubscribe<https://github.com/notifications/unsubscribe-auth/APONF2HNUYB733KX67QED6TXXSROPBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJLJONZXKZNENZQW2ZNLORUHEZLBMRPXI6LQMWBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTLDTOVRGUZLDORPXI6LQMWSUS43TOVS2M5DPOBUWG44SQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJVHEZTMMZQHEYTLAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDCOBWHE4DKMBQGIYKO5DSNFTWOZLSUZRXEZLBORSQ>. You are receiving this email because you are subscribed to this thread. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[ngump]

@Rachel ***@***.***> or @eva Dupont (BAP ***@***.***> to action the below request from Lou. Thanks, Nicole

…

________________________________ From: Lou Blick ***@***.***> Sent: Monday, August 28, 2023 10:14 AM To: microsoft/dynamics365patternspractices ***@***.***> Cc: Nicole Gump ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/dynamics365patternspractices] [AREA]: Process inbound goods (Issue #102) Please remove me from this GitHub project. I do no know why I am receiving these messages. Regards. -Lou [cid:5abe376d-7d46-47b5-969e-01729586c94b] Lou Blick Sr. Cloud Solution Architect, Azure Digital & App Innovation Microsoft Federal | Customer Success Unit [cid:f3868f23-0262-40f8-b6ca-34736665ce4c] W: 202-831-6416<tel:202-831-6416> | M: 202.669.2371<tel:202.669.2371> | E: ***@***.******@***.***> ***@***.***?anonymous&ep=signature>

________________________________ From: Nicole Gump ***@***.***> Sent: Monday, August 28, 2023 10:12 AM To: microsoft/dynamics365patternspractices ***@***.***> Cc: Subscribed ***@***.***> Subject: [microsoft/dynamics365patternspractices] [AREA]: Process inbound goods (Issue #102) Contact details ***@***.******@***.***> Organization type Microsoft employee End-to-end business process Inventory to deliver Specify the business process area name for the article. Process inbound goods Enter any additional comments or information you want us to know about this business process area. Looking for help on this business process area. Specify the date you expect the article to be completed and ready for review. 09/30/2023 Code of Conduct * I agree to follow this project's Code of Conduct — Reply to this email directly, view it on GitHub<#102> or unsubscribe<https://github.com/notifications/unsubscribe-auth/APONF2HNUYB733KX67QED6TXXSROPBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJLJONZXKZNENZQW2ZNLORUHEZLBMRPXI6LQMWBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTLDTOVRGUZLDORPXI6LQMWSUS43TOVS2M5DPOBUWG44SQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJVHEZTMMZQHEYTLAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDCOBWHE4DKMBQGIYKO5DSNFTWOZLSUZRXEZLBORSQ>. You are receiving this email because you are subscribed to this thread. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. — Reply to this email directly, view it on GitHub<#102 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASBCBGCXUGVPDMJ6JGFHYS3XXSRTLANCNFSM6AAAAAA4BPSENI>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[dj3500]

It looks like you guys have added like 6700 people to watch this repository. Removing some would be good.

[VonOgre]

I'm pretty sure that there's some default configuration to auto-subscribe everyone that's joined to the Microsoft organization when a new repo spins up.

…

On Mon, Aug 28, 2023, 7:25 AM Jakub Tarnawski ***@***.***> wrote: It looks like you guys have added like 6700 people to watch this repository. Removing some would be good. — Reply to this email directly, view it on GitHub <#102 (comment)> or unsubscribe <https://github.com/notifications/unsubscribe-auth/AENTWN6P2VH6AYF3I5E5BWTXXSS7NBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOJIFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVE2TSMZWGMYDSMJVQKSHI6LQMWSWS43TOVS2K5TBNR2WLKRRHA3DSOBVGAYDEMFHORZGSZ3HMVZKMY3SMVQXIZI> . You are receiving this email because you are subscribed to this thread. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .

[edupont04]

I don't know how 6000+ people got added as watchers of the repo, but I can't see a way to bulk-remove them.....

[edupont04]

I'll continue to investigate, but I recommend all 6000+ people to click the link to unsubscribe. Sadly, we're seeing a weak spot in user management on GitHub.

[arbyruns]

We might need to file https://aka.ms/reportitnow since this is going to my personal github\email account

[VonOgre]

FYI, the auto-watching is an account setting that can be disabled under "Notifications".

And you can update your watched repos from the same page (see View Watched Repositories)

[vainolo]

[surprised] Arieh Bibliowicz reacted to your message:

…

________________________________ From: Bryan Dunn ***@***.***> Sent: Monday, August 28, 2023 5:04:13 PM To: microsoft/dynamics365patternspractices ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [microsoft/dynamics365patternspractices] [AREA]: Process inbound goods (Issue #102) FYI, the auto-watching is an account setting that can be disabled. [image]<https://user-images.githubusercontent.com/18561847/263771010-ed03b20e-6a85-4c23-bba4-366a448340e7.png> And you can update your watched repos from the same page (see View Watched Repositories) [image]<https://user-images.githubusercontent.com/18561847/263771180-d91ff174-ab8a-44ff-b83e-45e9530c774a.png> — Reply to this email directly, view it on GitHub<#102 (comment)> or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAATTEXMU3JSIGULAQDA3XDXXTFRRBFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLLDTOVRGUZLDORPXI6LQMWWES43TOVSUG33NNVSW45FGORXXA2LDOOJIFJDUPFYGLKTSMVYG643JORXXE6NFOZQWY5LFVE2TSMZWGMYDSMJVQKSHI6LQMWSWS43TOVS2K5TBNR2WLKRRHA3DSOBVGAYDEMFHORZGSZ3HMVZKMY3SMVQXIZI>. You are receiving this email because you are subscribed to this thread. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[peterbom]

@VonOgre: If we're receiving notifications because we've been given push access to a repo, then wouldn't a more appropriate course of action be to revoke those permissions, rather than bulk unsubscribe us? I for one certainly shouldn't have push permission to this repo.

[ktoliver]

I'll continue to investigate, but I recommend all 6000+ people to click the link to unsubscribe. Sadly, we're seeing a weak spot in user management on GitHub.

@edupont04 This appears to be a result of a default option that's set when you create a new MicrosoftDocs repository in GitHub:

Each person who was automatically subscribed receives an auto-generated notification (if they have email notifications set up for their GitHub account).

I've found that the easiest way to unsubscribe to a repository when this happens is to use this link in the notification email (if your GitHub account is set up for email notifications):

[edupont04]

@ktoliver Yes, that's right. The problem is that each person must choose that unscubscribe link in the emails and/or unwatch the repo. In both cases, they'll need to sign in with their GitHub account, which fails for some....