Hi Team, There’s an Excel Feature that some customer and myself would like access to within Azure / Excel if possible. It’s called Power Fx and allows us to use Microsoft’s GPT3 within our Excel Desk App and I believe within Teams as well. What do we require in order to use it? ----- https://blogs.microsoft.com/ai/from-conversation-to-code-microsoft-introduces-its-first-product-features-powered-by-gpt-3/ With new features powered by GPT-3, Microsoft Power Apps users can describe a programming goal in conversational language and have it automatically transformed into Power Fx code.

Videos in Academy and Readiness need to have speed dial available in settings. Listening to slow speakers for a full 45 minutes. This one particular had good presenters but. . .slow and with accent. So if I'm trying to crunch and onboard/understand something quick . . .I'm in for a very long ride. Microsoft 365 and Security Learning Paths"" https://readiness.transform.microsoft.com/video-training-page/4ffd30b4-adc5-4090-91b0-1b61d14840fb/8649d3f3-2bca-43ef-8cae-658e1e0b1538

Hi team,

It would be great if you could include the forecast date in the Service usage report for any workload an FRP has a CPOR claim on. Currently we have to export multiple reports and then join them together to get a view on 15 and 40% forecast dates.

Having this information in the service usage would be useful as it will help with making sure forecast dates are accurate and will allow us to focus on bringing the adoption dates forward.

Cheers,

Currently, there is no visibility on Partner Center for the date on which a particular incentive milestone was achieved for any particular workload. It only shows as 'Reached' if a particular workload hits the incentive milestone. Can a feature be added where it provides the FRPs with visibility into the date of milestone fulfillment? This we greatly help in tracking of expected payouts in monthly invoices and provide clarity before rushing off to raise a dispute.

Alert/notification will automatically send to sender's manager email if the sender (internal user) send out email (labelled with sensitivity label) to external user. Sender's Manager means the specific manager that has been attributed in Azure AD/portal. Every single users in the tenant should have their own manager.

In coming period, MSFT will migrate from FTOP to Partner Center (OSU-M365).
It would be very helpfull if MSFT could share then API Framework (or future enhancements) to partners so they can integrate their internal systems.
If it would be possible to have a 2-way API that would even be super (for downloading and uploading relevant data).

>FTOP Task Details<上で掲載されている資料を>Microsoft 365 Specialty Partner Community<で検索しても見つかりません。
※以降、下記と表現します。
>FTOP Task Details<：①
>Microsoft 365 Specialty Partner Community<：②

これまでPlaybookは①で探していました。
しかし①のドキュメントは、今後は②に集約していくと認識しています。

①にあった資料の"タスク番号"を②で検索しても資料が見つかりません。
推奨の探し方、もしくは今後も①で資料を確認すべきなのか知りたいです。

また、英語版資料がローカライズされたタイミングや既存資料が更新されたタイミングで、Heads upで全ての資料が周知されるようになっているでしょうか？
もしくは、>Playbook Task Reference List<で今後も確認していくのがいいのでしょうか？

Today there is a FRP PowerBI dashboard that shows what other partners have claimed workloads for a customer that you have claimed a workload with. That information would ideally be available in Partner Center!

It would be ideal if we could see the Microsoft Account Team assigned to our customers, especially the MWA for S2500 Customers. 
 

More and more, we are finding that customers don't want to register or associate a different partner for a CPOR workload. Too often it is controversial, or another partner (LAR) might have a deal to have them all associated with them, or there might have been another partner that "also" had a role driving MAU and they don't want to switch. 

The net effect is that we aren't getting proper attribution for our role driving adoption and our monthly/quarterly/annual performance looks underwhelming. This also impacts how we are rewarded through the incentive model and can negatively impact how we are graded from a compliance standpoint. This may not be impacting all partners, but at last count we've only been able to register 1/20 engagements in the last 3-4 months where technically we are driving adoption or advancing the cause! In my experience, the friction is real and causing the whole CPOR registration to not work for us. 

I have a few suggestions to consider:
1. Perhaps it is time to reconsider the business rule that only one partner can be associated to a workload. What if by design, rather than by exception, multiple partners could be assigned to a workload? That would remove some of the friction that customers face accepting a new request.

2. What if there was a simpler way to confirm a partner is engaged? Currently, we need to either have a customer sign a document or we need to submit a signed SOW as POE. As a partner, we often don't feel comfortable submitting an entire SOW as it contains a lot of detail that is under NDA.

Secondly, we worry that if we just submitted the SOW without first talking to the customer, they would be upset receiving the email notification from Microsoft as it is confusing and possibly triggers the multi-partner association issue. Instead of it being a "notification of partner association", perhaps it could be reworded to "Confirmation of Partner Engagement" and the language could say, "Congratulations, we understand you have retained the support of <partner name> and in your work together you may be driving the adoption of the following areas: <list the areas> 
To support your work together, we will provide limited adoption data of these workloads with your partner. If you would prefer not to disclose this data, or have the partner associated in our records as providing support, please click here. Otherwise, nothing is required in response.  

3. Another great option would be for Microsoft CSM or Modern Workplace Specialist to be allowed to "vouch" for our engagement. Perhaps the partner could request someone on the Account Team to confirm that the partner is engaged and is driving adoption/MAU. 

4. I'd recommend that any MCAP POE count as CPOR POE for key workloads that relate to the engagement. We've had many MCAP engagements that were influential at moving a customer forward, but for various reasons we weren't able to get associated to that customer for the workloads in question.