This living space exudes a perfect blend of modern elegance and warmth. The living room features a spacious sectional sofa in a neutral gray tone, complemented by plush cushions and a soft, textured rug that anchors the seating area. A sleek, low-profile coffee table with a glass top adds a touch of sophistication, while two cozy accent chairs in muted mustard tones provide a splash of color. Large windows allow natural light to flood the room, enhancing the airy, open feel. A stylish entertainment unit with minimalist shelving displays a curated selection of books and decor pieces From Eve Furniture

Moving into the dining area, a beautiful wooden dining table with a natural oak finish serves as the focal point. Surrounding it are elegantly upholstered dining chairs with dark wooden legs, offering comfort and style. Above the table, a statement chandelier adds a modern edge while softly illuminating the space.

New Era Furniture

In the bedroom, the centerpiece is a luxurious king-sized bed with an upholstered headboard in a rich navy fabric. Crisp white linens and layered throws create a cozy, inviting feel. Matching nightstands with brass accents sit on either side of the bed, each topped with chic table lamps. A spacious, built-in wardrobe offers ample storage without overpowering the room, maintaining a clean, uncluttered aesthetic. New Era Furniture

​This living space exudes a perfect blend of modern elegance and warmth. The living room features a spacious sectional sofa in a neutral gray tone, complemented by plush cushions and a soft, textured rug that anchors the seating area. A sleek, low-profile coffee table with a glass top adds a touch of sophistication, while two cozy accent chairs in muted mustard tones provide a splash of color. Large windows allow natural light to flood the room, enhancing the airy, open feel. A stylish entertainment unit with minimalist shelving displays a curated selection of books and decor pieces From Eve Furniture Moving into the dining area, a beautiful wooden dining table with a natural oak finish serves as the focal point. Surrounding it are elegantly upholstered dining chairs with dark wooden legs, offering comfort and style. Above the table, a statement chandelier adds a modern edge while softly illuminating the space.New Era FurnitureIn the bedroom, the centerpiece is a luxurious king-sized bed with an upholstered headboard in a rich navy fabric. Crisp white linens and layered throws create a cozy, inviting feel. Matching nightstands with brass accents sit on either side of the bed, each topped with chic table lamps. A spacious, built-in wardrobe offers ample storage without overpowering the room, maintaining a clean, uncluttered aesthetic. New Era Furniture  Read More

​

I have one very large database that I only want to backup once a week so I’m wondering if the Cleanup Task is going to remove because the current maintenance plan is set to delete after 2 days.

​I have one very large database that I only want to backup once a week so I’m wondering if the Cleanup Task is going to remove because the current maintenance plan is set to delete after 2 days.  Read More

​

We’re excited to introduce a weekly spotlight on various topics within our Microsoft Fraud Protection Tech Community to help you maximize the benefits of Microsoft Dynamics Fraud Protection (DFP). This week, we’re continuing our focus on commonly asked questions about DFP ‘Rules’ which you can check out the Q&A details here:  

If you have any questions, please feel free to reach out in the Fraud Protection Tech Community. Your feedback is incredibly valuable to us. 

Best, 

DFP Product Team 

—————— 

 
1. How do we know the rule work as expected before going to production?  

Before deploying rules to production in Microsoft Dynamics 365 Fraud Protection, it’s essential to test them thoroughly to ensure they work as expected. Here’s how you can validate your rules:  

Utilize the sandbox (INT) environment for functional and integration testing. This allows for safe testing of new configurations, rules, and features without affecting the live production environment.  

Test rules in the sandbox environment to validate their logic and outcomes. Keep in mind that the scores generated in the sandbox should not be assumed to have real meaning, as the models only see test traffic.  

Consider using observe mode to see what is returned by the rules without making actual decisions.  
The sandbox environment is for testing purposes. It is not scaled for high load and is not suitable for performance or stress testing.  

You can manage rules in a specific environment of Dynamics 365 Fraud Protection without impacting the production environment. This includes creating branches on the Rules tab, where each branch represents a collection of rules. The default branch is the Production branch, which is executed whenever traffic is sent to an assessment.  

For detailed guidance on rule testing and deployment, you can refer to the official documentation on Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn 

2. Do you have ‘rule builder’ or equivalent capability to allow customer to define complex rules without vendor support?  

Yes, Microsoft Dynamics 365 Fraud Protection includes a ‘rule builder’ capability that allows customers to define complex rules without vendor support. This feature is part of the rules management system within Dynamics 365 Fraud Protection and provides the flexibility to create custom rules based on various inputs such as attributes from the API request, scores from AI models, uploaded lists, defined velocities, external calls, and functions created within Fraud Protection.  

The official Microsoft documentation describes the process of defining a rule using the RETURN and WHEN keywords, allowing for the creation of custom rules that can convert an assessment into a decision, such as Approve, Reject, Review, or Challenge. This system gives customers the ability to manage rules in specific environments using the environment switcher, and rules can be created and managed on the Rules tab for purchases, account creation, or account login.  

References:  

Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn  

3. What’s MS DFP approach for reusing rules/velocity sets from either alternative Fraud Solutions or in-house Solutions?  

DFP allows merchants to create their own rules based on the industry type. Rules and velocities can be cloned within the same assessment (AP, PP) to be reused and modified. If a merchant is using another fraud solution in addition to DFP, they can write equivalent rules using our Fraud Query Language (FQL).  

 4. How are Rules Clauses structured in Dynamics 365 Fraud Protection? 

Clauses are structured using the RETURN and WHEN keywords, where RETURN specifies the decision and WHEN specifies the condition. Each rule must contain at least one clause, and each clause is assigned a unique name. 

References: 

Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn 

5. Would a new rule affect transactions in an old/existing queue?  

In Microsoft Dynamics 365 Fraud Protection, when you create a new rule, it typically applies to transactions going forward from the point of activation. Existing queues, which contain transactions that were processed before the new rule was implemented, would not be retroactively affected by this new rule. The new rule would only affect transactions that are processed after the rule has been activated and would not change the status of transactions that are already in an old or existing queue.  

However, if you need to apply new rules to transactions in an existing queue, you may need to manually review those transactions or reprocess them under the new rule set, if such functionality is supported by the system. It’s important to note that manual intervention should be done carefully to avoid disrupting the customer experience or affecting the integrity of the transaction data.  

For specific guidance on how new rules interact with existing queues and transactions, you can refer to the official documentation on Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn  

6. Are rules case sensitive?  

In Microsoft Dynamics 365 Fraud Protection, rule names must be unique and they are case-insensitive.  This means that when you create or reference rule names, the system does not differentiate between uppercase and lowercase letters. However, it’s important to note that while rule names are case-insensitive, the string operations within the rules themselves may be case-sensitive by default and may require specific functions like .ToUpper() to ensure case-insensitive comparison   

For example, if you have a rule named “CheckFraud” and you try to create another rule named “checkfraud,” the system will recognize them as the same due to the case-insensitivity of rule names. But when writing conditions within the rules, you might need to consider the case sensitivity of the attributes you are comparing.  

For more detailed information on rule management and best practices, you can refer to the official Microsoft Dynamics 365 Fraud Protection documentation here: Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn.  

7. Why is this challenge rule not working?  

To troubleshoot why a challenge rule in Microsoft Dynamics 365 Fraud Protection is not working as expected, you can follow these steps:  

Review the Rule Configuration: Ensure that the rule is correctly defined with the RETURN and WHEN keywords. The RETURN statement should specify Challenge as the action and it is only executed if the WHEN statement evaluates to True.  

Check the Conditions: Verify that the conditions set in the WHEN statement are accurate and that they use the correct attributes from the API request for the assessment. These attributes can include custom data and should be accessed with the @ operator.  

Examine the Rule Evaluations: Look into the ruleEvaluations section included in the assessment API response. This section provides a list of each rule and clause that was evaluated for a transaction, which can help identify where the rule might be failing.  

Monitor the Rule Performance: Utilize the monitoring dashboards to check the rule challenged rate – the percentage of assessed transactions by count that were challenged. This can give insights into the rule’s performance and whether it is being triggered as expected. [1]  
Consult the Documentation: Refer to the official Microsoft documentation on managing rules in Dynamics 365 Fraud Protection for a comprehensive guide on rule creation and management. [2]  

References:  

[1] Monitoring – Dynamics 365 Fraud Protection | Microsoft Learn  

[2] Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn  

8. Some transactions went through that by everything we can see should have been caught by a rule.  What are the steps I should take to troubleshoot?   

When transactions that should have been caught by a rule in Microsoft Dynamics 365 Fraud Protection slip through, it’s important to conduct a thorough investigation to understand why the rule did not trigger as expected. Here are the steps you can take to troubleshoot:  

Review the Rule Configuration: Ensure that the rule is correctly set up with the appropriate conditions and actions. Check for any logical errors or misconfigurations that might have caused the rule to not trigger.  

Check the Conditions: Verify that the conditions set in the WHEN statement are accurate and that they use the correct attributes from the API request for the assessment. These attributes can include custom data and should be accessed with the @ operator.  

Examine the Transactions: Look at the details of the transactions that were not caught by the rule. Compare them against the rule’s criteria to see if there’s a mismatch or if the transactions have any common attributes that were not considered in the rule.  

Check Rule Evaluations: In the assessment API response, there is a ruleEvaluations section that provides a list of each rule and clause that was evaluated for a transaction. This can help identify where the rule might be failing.  

Monitor Rule Performance: Use the monitoring dashboards to check the rule’s performance metrics, such as the challenged rate, to gain insights into how often the rule is being triggered.  

Review Integration: If you have integrated Dynamics 365 Fraud Protection with other systems, verify that the integration is functioning correctly and that data is being passed accurately between systems.  
Consult the Documentation: Refer to the official Microsoft documentation on managing rules in Dynamics 365 Fraud Protection for a comprehensive guide on rule creation and management. [1]  

References:  

[1] Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn  

9. Can you find out the common rules for the transactions that had the highest scores? 

In Microsoft Dynamics 365 Fraud Protection, transactions with the highest risk scores are those that are most likely to be fraudulent. The common rules applied to these transactions are designed to identify and prevent high-risk activities. Here are some of the rules that are commonly used:  

Threshold rules: These rules reject transactions that exceed a certain risk score. For example, transactions for gift cards might be rejected if the risk score is above 400.  

Velocity rules: These rules identify and block rapid, repeated transactions from the same entity, which could indicate fraudulent behavior.  

List checks: These rules compare transaction data against lists of known fraud indicators, such as device fingerprints or IP addresses.  
Anomaly detection: These rules look for patterns of behavior that are unusual and deviate from the norm, which could indicate fraud.  

For a more detailed understanding of the common rules applied to high-scoring transactions, you may want to review the “Score analyst reports” in the Dynamics 365 Fraud Protection portal, which can provide insights into the relationship between Fraud Protection scores and the rules that were executed. If you need further assistance or have specific questions you can also contact Microsoft support or your Microsoft authorized partner for additional assistance.  

References:  

Score analyst reports – Dynamics 365 Fraud Protection | Microsoft Learn  

10. The Rule evaluation behavior is currently set to “Run only the first matching rule”, and we’re trying to get it set to “Run all matching rules until a decision is made”.  This setting is set in the sandbox environment, but for some reason, we’re not able to set it in the prod environment. Can you help?  

To change the Rule evaluation behavior in Microsoft Dynamics 365 Fraud Protection from “Run only the first matching rule” to “Run all matching rules until a decision is made,” you should be able to do so through the environment settings. However, if you’re encountering issues changing this setting in the production environment, here are some steps you can take:  

Check User Permissions: Ensure that you have the necessary permissions to make changes to the production environment settings. You may need to have admin rights or specific roles assigned to your user account.  

Review Environment Configuration: Make sure that the production environment is properly configured and that there are no locks or restrictions in place that might prevent changes to the rule evaluation behavior.  
Consult Documentation: Refer to the official Microsoft documentation for Dynamics 365 Fraud Protection, which provides detailed instructions on managing rules and environment settings.  

References:  

Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn  

​ 
We’re excited to introduce a weekly spotlight on various topics within our Microsoft Fraud Protection Tech Community to help you maximize the benefits of Microsoft Dynamics Fraud Protection (DFP). This week, we’re continuing our focus on commonly asked questions about DFP ‘Rules’ which you can check out the Q&A details here:  
 
If you have any questions, please feel free to reach out in the Fraud Protection Tech Community. Your feedback is incredibly valuable to us. 
 
Best, 
DFP Product Team 
 
—————— 
 1. How do we know the rule work as expected before going to production?  
 
Before deploying rules to production in Microsoft Dynamics 365 Fraud Protection, it’s essential to test them thoroughly to ensure they work as expected. Here’s how you can validate your rules:  

Utilize the sandbox (INT) environment for functional and integration testing. This allows for safe testing of new configurations, rules, and features without affecting the live production environment.  

Test rules in the sandbox environment to validate their logic and outcomes. Keep in mind that the scores generated in the sandbox should not be assumed to have real meaning, as the models only see test traffic.  

Consider using observe mode to see what is returned by the rules without making actual decisions.  
The sandbox environment is for testing purposes. It is not scaled for high load and is not suitable for performance or stress testing.  

You can manage rules in a specific environment of Dynamics 365 Fraud Protection without impacting the production environment. This includes creating branches on the Rules tab, where each branch represents a collection of rules. The default branch is the Production branch, which is executed whenever traffic is sent to an assessment.  
  
For detailed guidance on rule testing and deployment, you can refer to the official documentation on Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn 
 
2. Do you have ‘rule builder’ or equivalent capability to allow customer to define complex rules without vendor support?  
 
Yes, Microsoft Dynamics 365 Fraud Protection includes a ‘rule builder’ capability that allows customers to define complex rules without vendor support. This feature is part of the rules management system within Dynamics 365 Fraud Protection and provides the flexibility to create custom rules based on various inputs such as attributes from the API request, scores from AI models, uploaded lists, defined velocities, external calls, and functions created within Fraud Protection.  
  
The official Microsoft documentation describes the process of defining a rule using the RETURN and WHEN keywords, allowing for the creation of custom rules that can convert an assessment into a decision, such as Approve, Reject, Review, or Challenge. This system gives customers the ability to manage rules in specific environments using the environment switcher, and rules can be created and managed on the Rules tab for purchases, account creation, or account login.  
  
References:  

Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn  

 3. What’s MS DFP approach for reusing rules/velocity sets from either alternative Fraud Solutions or in-house Solutions?  
 
DFP allows merchants to create their own rules based on the industry type. Rules and velocities can be cloned within the same assessment (AP, PP) to be reused and modified. If a merchant is using another fraud solution in addition to DFP, they can write equivalent rules using our Fraud Query Language (FQL).  
 
 
 4. How are Rules Clauses structured in Dynamics 365 Fraud Protection? 
 
Clauses are structured using the RETURN and WHEN keywords, where RETURN specifies the decision and WHEN specifies the condition. Each rule must contain at least one clause, and each clause is assigned a unique name. 
 
References: 

Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn 

5. Would a new rule affect transactions in an old/existing queue?  
 
In Microsoft Dynamics 365 Fraud Protection, when you create a new rule, it typically applies to transactions going forward from the point of activation. Existing queues, which contain transactions that were processed before the new rule was implemented, would not be retroactively affected by this new rule. The new rule would only affect transactions that are processed after the rule has been activated and would not change the status of transactions that are already in an old or existing queue.  
 
However, if you need to apply new rules to transactions in an existing queue, you may need to manually review those transactions or reprocess them under the new rule set, if such functionality is supported by the system. It’s important to note that manual intervention should be done carefully to avoid disrupting the customer experience or affecting the integrity of the transaction data.  
 
For specific guidance on how new rules interact with existing queues and transactions, you can refer to the official documentation on Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn  
 
 
6. Are rules case sensitive?  
 
In Microsoft Dynamics 365 Fraud Protection, rule names must be unique and they are case-insensitive.  This means that when you create or reference rule names, the system does not differentiate between uppercase and lowercase letters. However, it’s important to note that while rule names are case-insensitive, the string operations within the rules themselves may be case-sensitive by default and may require specific functions like .ToUpper() to ensure case-insensitive comparison   
  
For example, if you have a rule named “CheckFraud” and you try to create another rule named “checkfraud,” the system will recognize them as the same due to the case-insensitivity of rule names. But when writing conditions within the rules, you might need to consider the case sensitivity of the attributes you are comparing.  
  
For more detailed information on rule management and best practices, you can refer to the official Microsoft Dynamics 365 Fraud Protection documentation here: Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn.  
 7. Why is this challenge rule not working?  
 
To troubleshoot why a challenge rule in Microsoft Dynamics 365 Fraud Protection is not working as expected, you can follow these steps:  

Review the Rule Configuration: Ensure that the rule is correctly defined with the RETURN and WHEN keywords. The RETURN statement should specify Challenge as the action and it is only executed if the WHEN statement evaluates to True.  

Check the Conditions: Verify that the conditions set in the WHEN statement are accurate and that they use the correct attributes from the API request for the assessment. These attributes can include custom data and should be accessed with the @ operator.  

Examine the Rule Evaluations: Look into the ruleEvaluations section included in the assessment API response. This section provides a list of each rule and clause that was evaluated for a transaction, which can help identify where the rule might be failing.  

Monitor the Rule Performance: Utilize the monitoring dashboards to check the rule challenged rate – the percentage of assessed transactions by count that were challenged. This can give insights into the rule’s performance and whether it is being triggered as expected. [1]  
Consult the Documentation: Refer to the official Microsoft documentation on managing rules in Dynamics 365 Fraud Protection for a comprehensive guide on rule creation and management. [2]  

References:  

[1] Monitoring – Dynamics 365 Fraud Protection | Microsoft Learn  

[2] Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn  

 8. Some transactions went through that by everything we can see should have been caught by a rule.  What are the steps I should take to troubleshoot?   
 
When transactions that should have been caught by a rule in Microsoft Dynamics 365 Fraud Protection slip through, it’s important to conduct a thorough investigation to understand why the rule did not trigger as expected. Here are the steps you can take to troubleshoot:  

Review the Rule Configuration: Ensure that the rule is correctly set up with the appropriate conditions and actions. Check for any logical errors or misconfigurations that might have caused the rule to not trigger.  

Check the Conditions: Verify that the conditions set in the WHEN statement are accurate and that they use the correct attributes from the API request for the assessment. These attributes can include custom data and should be accessed with the @ operator.  

Examine the Transactions: Look at the details of the transactions that were not caught by the rule. Compare them against the rule’s criteria to see if there’s a mismatch or if the transactions have any common attributes that were not considered in the rule.  

Check Rule Evaluations: In the assessment API response, there is a ruleEvaluations section that provides a list of each rule and clause that was evaluated for a transaction. This can help identify where the rule might be failing.  

Monitor Rule Performance: Use the monitoring dashboards to check the rule’s performance metrics, such as the challenged rate, to gain insights into how often the rule is being triggered.  

Review Integration: If you have integrated Dynamics 365 Fraud Protection with other systems, verify that the integration is functioning correctly and that data is being passed accurately between systems.  
Consult the Documentation: Refer to the official Microsoft documentation on managing rules in Dynamics 365 Fraud Protection for a comprehensive guide on rule creation and management. [1]  

References:  

[1] Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn  

 9. Can you find out the common rules for the transactions that had the highest scores? 
 
In Microsoft Dynamics 365 Fraud Protection, transactions with the highest risk scores are those that are most likely to be fraudulent. The common rules applied to these transactions are designed to identify and prevent high-risk activities. Here are some of the rules that are commonly used:  

Threshold rules: These rules reject transactions that exceed a certain risk score. For example, transactions for gift cards might be rejected if the risk score is above 400.  

Velocity rules: These rules identify and block rapid, repeated transactions from the same entity, which could indicate fraudulent behavior.  

List checks: These rules compare transaction data against lists of known fraud indicators, such as device fingerprints or IP addresses.  
Anomaly detection: These rules look for patterns of behavior that are unusual and deviate from the norm, which could indicate fraud.  

For a more detailed understanding of the common rules applied to high-scoring transactions, you may want to review the “Score analyst reports” in the Dynamics 365 Fraud Protection portal, which can provide insights into the relationship between Fraud Protection scores and the rules that were executed. If you need further assistance or have specific questions you can also contact Microsoft support or your Microsoft authorized partner for additional assistance.  
  
References:  

Score analyst reports – Dynamics 365 Fraud Protection | Microsoft Learn  

 10. The Rule evaluation behavior is currently set to “Run only the first matching rule”, and we’re trying to get it set to “Run all matching rules until a decision is made”.  This setting is set in the sandbox environment, but for some reason, we’re not able to set it in the prod environment. Can you help?  
 
To change the Rule evaluation behavior in Microsoft Dynamics 365 Fraud Protection from “Run only the first matching rule” to “Run all matching rules until a decision is made,” you should be able to do so through the environment settings. However, if you’re encountering issues changing this setting in the production environment, here are some steps you can take:  

Check User Permissions: Ensure that you have the necessary permissions to make changes to the production environment settings. You may need to have admin rights or specific roles assigned to your user account.  

Review Environment Configuration: Make sure that the production environment is properly configured and that there are no locks or restrictions in place that might prevent changes to the rule evaluation behavior.  
Consult Documentation: Refer to the official Microsoft documentation for Dynamics 365 Fraud Protection, which provides detailed instructions on managing rules and environment settings.  

References:  

Manage rules – Dynamics 365 Fraud Protection | Microsoft Learn  

 
 
 
 
   Read More

​

I am generating a new Microsoft Sharepoint List and I have several questions. I think I will make individual posts here on learn.microsoft.com where each post addresses an individual question or issue. This post, I intend, will address the auto-save issue and feature.
As I add content to my Microsoft List, is the data automatically saved? I assume that there might be some way to automatically add a large number of virtually blank rows with an auto-incrementing index (aka title) column. But I thought it would save time to just record and run a macro script to add a large number of rows. I did this on my work laptop which I took home to continue the operation. To my disappointment, when I went to work and rebooted my laptop computer and opened this list, the large number of added rows were not there.
Why is this?

Isn’t there some sort of automatic save mechanism at play?

As I suggested, I was working off of a laptop computer that I moved from work to home. Maybe this has something to do with what went wrong. Maybe disconnecting from one server and then attaching to another caused a security flag to be thrown.

​I am generating a new Microsoft Sharepoint List and I have several questions. I think I will make individual posts here on learn.microsoft.com where each post addresses an individual question or issue. This post, I intend, will address the auto-save issue and feature.As I add content to my Microsoft List, is the data automatically saved? I assume that there might be some way to automatically add a large number of virtually blank rows with an auto-incrementing index (aka title) column. But I thought it would save time to just record and run a macro script to add a large number of rows. I did this on my work laptop which I took home to continue the operation. To my disappointment, when I went to work and rebooted my laptop computer and opened this list, the large number of added rows were not there.Why is this? Isn’t there some sort of automatic save mechanism at play? As I suggested, I was working off of a laptop computer that I moved from work to home. Maybe this has something to do with what went wrong. Maybe disconnecting from one server and then attaching to another caused a security flag to be thrown.  Read More

​

Hello Team,

I am currently developing a bot-to-bot VOIP call feature using Microsoft Teams and have encountered critical issue that I need assistance with on urgent basis

1. Call Not Found Error

Despite the call being established successfully, when I attempt to retrieve the call status using the API, I receive a “Call Not Found” error. This occurs even when I confirm that the call is active.

Steps to Reproduce:

Initiate a call between two registered bots.After the call is established, invoke the API to fetch the call status.Observe the error response.

https://graph.microsoft.com/v1.0/communications/calls/46005a80-5155-4600-8338-da94acce1473/answer

Body

​Hello Team,I am currently developing a bot-to-bot VOIP call feature using Microsoft Teams and have encountered critical issue that I need assistance with on urgent basis1. Call Not Found ErrorDespite the call being established successfully, when I attempt to retrieve the call status using the API, I receive a “Call Not Found” error. This occurs even when I confirm that the call is active.Steps to Reproduce:Initiate a call between two registered bots.After the call is established, invoke the API to fetch the call status.Observe the error response.https://graph.microsoft.com/v1.0/communications/calls/46005a80-5155-4600-8338-da94acce1473/answerBody{  “callbackUri”: “https://domain.ngrok-free.app/callback”,  “mediaConfig”: {    “blob”: “<Media Session Configuration Blob>”,    “@odata.type”: “#microsoft.graph.appHostedMediaConfig”  },  “acceptedModalities”: [    “audio”  ],  “callOptions”: {    “isContentSharingNotificationEnabled”: true,    “isDeltaRosterEnabled”: true,    “@odata.type”: “#microsoft.graph.incomingCallOptions”  },  “participantCapacity”: 200} {    “error”: {        “code”: “8522”,        “message”: “Call not found.”,        “innerError”: {            “date”: “2024-10-23T19:17:17”,            “request-id”: “ecff1740-843f-49dc-8c6b-1a65a2c93010”,            “client-request-id”: “ecff1740-843f-49dc-8c6b-1a65a2c93010”        }    }}  Read More

​

I am currently developing a bot-to-bot VOIP call feature using Microsoft Teams and have encountered critical issues that I need assistance with: Please suggest

We have registered 2 bots in the same tenant with separate APP Registrations, As per the documentation sending a body to initiate VOIP calls between the bots however it is not working and getting the below error. 

When trying to make bot-to-bot calls, I consistently receive a “Request authorization tenant mismatch” error, despite both bots being registered under the same tenant.

Steps to Reproduce:

Register two bots in the same Azure tenant.Use the Microsoft Graph API to initiate a call from one bot to the other.Observe the error response.

https://graph.microsoft.com/v1.0/communications/calls?Content-Type=application/json

Error Message:

​I am currently developing a bot-to-bot VOIP call feature using Microsoft Teams and have encountered critical issues that I need assistance with: Please suggestWe have registered 2 bots in the same tenant with separate APP Registrations, As per the documentation sending a body to initiate VOIP calls between the bots however it is not working and getting the below error.  When trying to make bot-to-bot calls, I consistently receive a “Request authorization tenant mismatch” error, despite both bots being registered under the same tenant.Steps to Reproduce:Register two bots in the same Azure tenant.Use the Microsoft Graph API to initiate a call from one bot to the other.Observe the error response. https://graph.microsoft.com/v1.0/communications/calls?Content-Type=application/json {  “@odata.type”: “#microsoft.graph.call”,  “callbackUri”: “https://7084-&&&&&-234.ngrok-free.app/callback”,  “source”: {    “@odata.type”: “#microsoft.graph.participantInfo”,    “identity”: {      “@odata.type”: “#microsoft.graph.identitySet”,      “application”: {        “@odata.type”: “#microsoft.graph.identity”,        “displayName”: “VOIP Call Bot”,        “id”: “BOT 1 APP ID”      }    },    “region”: null,    “languageId”: null  },  “targets”: [    {      “@odata.type”: “#microsoft.graph.invitationParticipantInfo”,      “identity”: {        “@odata.type”: “#microsoft.graph.identitySet”,        “application”: {          “@odata.type”: “#microsoft.graph.identity”,          “displayName”: “Calling_Teams_Bot”,          “id”: “APP ID”,          “tenantId”: “BOT 1 APP Tenant ID”        }      }    }  ],  “requestedModalities”: [    “audio”  ],  “tenantId”: “BOT 1 APP Tenant ID”,  “mediaConfig”: {    “@odata.type”: “#microsoft.graph.serviceHostedMediaConfig”  }} Error Message: {    “error”: {        “code”: “7505”,        “message”: “Request authorization tenant mismatch.”,        “innerError”: {            “date”: “2024-10-23T18:28:10”,            “request-id”: “66dd5026-763a-46bc-9a94-79cf0630ed33”,            “client-request-id”: “66dd5026-763a-46bc-9a94-79cf0630ed33”        }    }}  Read More

​

We’re pleased to announce that Sheet Protection is now available on iPad! Excel users will now be able to Pause or Resume Sheet Protection, Manage Sheet Protection, as well Edit locked or unlocked ranges just like on Excel Desktop or Excel for the Web.

Invoke, Pause, and Resume

Sheet Protection can be activated from either the Sheet tab or the Ribbon. Click on the Sheet tab with the lock icon and then select the “Protection…” option in the floating UI. Alternatively, you can navigate to Review > Protection in the Ribbon to access the Sheet Protection feature.
Next, to temporarily disable protection on a protected sheet, click “Pause Sheet Protection”. To re-enable it, click “Resume Sheet Protection”. If a password was previously set, you will need to enter it again to proceed.

Pause and Resume Sheet Protection

Manage and allow edit ranges

Choose the “Manage Sheet Protection” option to adjust the sheet’s protection settings. This feature enables you to modify the password, tweak protection options, and add, edit, or remove edit ranges.

Manage Sheet Protection

Availability

To use this feature, install Excel on iPad Version 2.90.930.0 or later.

Don’t have it yet? It’s probably us, not you. Features are released over time to ensure things are working smoothly. We highlight features that you may not have because they’re slowly releasing to larger numbers of users. Sometimes we remove elements for further improvement based on your feedback. Though this is rare, we also reserve the option to pull a feature entirely out of the product even if you have had the opportunity to try it.

Sharing feedback

We hope you like this new addition to Excel on iPad and we’d love to hear what you think about it! Settings > Help & Feedback, then select “Tell Us What You Like” or “Tell Us What Can Be Better.”

Thanks,
The Excel iPad Sheet Protection crew

​Microsoft Tech Community – Latest Blogs –Read More 

For the past few weeks users have had issues with new pop up windows in office apps not displaying on screen. This is mostly in the remote app view. For instance I can be looking at my inbox in outlook via azure virtual desktop remote app and double click on an email to pop it out or reply and the new window displays on screen but does not display correctly or respond correctly. You need to shift+right click on the window on the taskbar and restore it or windows key+arrow key to display correctly. We have this issue pretty consistently with other apps as well.

​For the past few weeks users have had issues with new pop up windows in office apps not displaying on screen. This is mostly in the remote app view. For instance I can be looking at my inbox in outlook via azure virtual desktop remote app and double click on an email to pop it out or reply and the new window displays on screen but does not display correctly or respond correctly. You need to shift+right click on the window on the taskbar and restore it or windows key+arrow key to display correctly. We have this issue pretty consistently with other apps as well.  Read More

​

Question about universal print in GCC.  The MS site states that with G3 or G5 you also need the “extra features sku” or windows ols activation sku.  Do you know what the “extra features” sku is?  The site has no further mention of it and I cant find anything else on the topic.  If we have to go windows ols, that is only available through open value?  

​Question about universal print in GCC.  The MS site states that with G3 or G5 you also need the “extra features sku” or windows ols activation sku.  Do you know what the “extra features” sku is?  The site has no further mention of it and I cant find anything else on the topic.  If we have to go windows ols, that is only available through open value?    Read More

​

We are excited to announce the General Availability of Azure OpenAI Global Batch offering, designed to handle large-scale and high-volume processing tasks efficiently. Process asynchronous groups of requests with separate quota, a 24-hour turnaround time, at 50% less cost than global standard.

This is a quote from one of our customers:

 ”Ontada is at the unique position of serving providers, patients and life science partners with data-driven insights. We leverage the Azure OpenAI batch API to process tens of millions of unstructured documents efficiently, enhancing our ability to extract valuable clinical information. What would have taken months to process now takes just a week. This significantly improves evidence-based medicine practice and accelerates life science product R&D. Partnering with Microsoft, we are advancing AI-driven oncology research, aiming for breakthroughs in personalized cancer care and drug development.”

 Sagran Moodley, Chief Innovation and Technology Officer, Ontada

 Why Azure OpenAI Global Batch?

Benefit 50% lower costs, enabling you to either introduce new workloads or run existing workloads more frequently, thereby increasing overall business value.
Efficiently handle large-scale workloads that would be impractical to process in real-time, significantly reducing processing times.
Minimize engineering overhead for job management with a high resource quota, allowing you to queue and process gigabytes of data with ease. Substantially high quotas for batch.

New feature: Dynamic Quota – no more quota exceed errors!

When you enable dynamic quota for your deployments, you can opportunistically take advantage of more quota when extra capacity is available.!

Supported Models

The following models currently support the global batch:

Model

Supported Versions

gpt4o

2024-08-06

gpt4o

2024-05-13

gpt-4o-mini

2024-07-18

gpt-4

turbo-2024-04-09

gpt-4

0613

gpt-35-turbo

0125

gpt-35-turbo

1106

gpt-35-turbo

0613

For the most up-to-date information on regions and models, please refer to our models page.

Key Use Cases

The Azure OpenAI Batch API opens up new possibilities across various industries and applications:

Large-Scale Data Processing: Quickly analyze extensive datasets in parallel, enabling faster decision-making and insights.
Content Generation: Automate the creation of large volumes of text, such as product descriptions, articles, and more.
Document Review and Summarization: Streamline the review and summarization of lengthy documents, saving valuable time and resources.
Customer Support Automation: Enhance customer support by handling numerous queries simultaneously, ensuring faster and more efficient responses.
Data Extraction and Analysis: Extract and analyze information from vast amounts of unstructured data, unlocking valuable insights.
Natural Language Processing (NLP) Tasks: Perform sentiment analysis, translation, and other NLP tasks on large datasets effortlessly.
Marketing and Personalization: Generate personalized content and recommendations at-scale, improving engagement and customer satisfaction.

Getting Started

Ready to try Azure OpenAI Batch API? Take it for a spin here.

Learn more

Using images in your batch input

Default batch token quota allocation and requesting increase

Supported regions

​Microsoft Tech Community – Latest Blogs –Read More